Be sure to check out the  Top 10 viewed SAP Notes for May 2013  for the SAP Financial Consolidation Suite!

Cashed Check Step  with Txt File

Purpose

If your bank sends you information about your cashed checks electronic means (a file on disk for example) you can import this data into your system using program RFEBCK00 (after first converting it to SAP format).

Trigger

In both of the above cases, postings are made from the outgoing checks account to the bank account. In addition, the date on which the check was cashed is recorded in the check information file.

initial screen

click on execute button

Go to SM35 and process batch input session

view the accounting entries

following is the Txt Format file as per the attachment if you like this document then please reward this post

thanks

Trinath

We can use parallel ledgers in asset accounting for different valuations as per different accounting principles. In our scenario, company code AIPL (Hindustan Mills Ltd) follows two accounting principles that is US GAAP and Indian GAAP. In General Ledger accounting we have created ledgers for each GAAP i.e. leading ledger ‘0L’ for US GAAP and Non-leading ledger ‘X1’ for Indian GAAP. In asset accounting, we use master area i.e. area 01 for leading ledger valuation. For valuation of non-leading ledger, we create one separate real depreciation area and one derived depreciation area for each accounting principle so that the values of Asset Accounting and General Ledger Accounting can be reconciled. The derived depreciation area triggers adjustment postings to keep the general ledger and subsidiary ledgers in sync. We have already created ledger group for each ledger in General Ledger accounting, the same ledger group will be assigned in depreciation area of each accounting principle in asset accounting. The following depreciation areas will be created:

1. Define Depreciation Areas

Define depreciation area 1 (book depreciation area ) and 30 (depreciation area for Indian GAAP). For depreciation area 1, system posts value in real time whereas for depreciation area 30, system posts only depreciation value. Use following menu path or transaction code:

Using above menu path or T.code we will assign the ledger groups in the respective depreciation area i.e. ledger group '0L' in area 1 and ledger 'X1' in area 30:

In the above step, we have specified ledger group ‘0L’ as target ledger group for master depreciation area 01 that means asset values of depreciation area 01 will be updated in leading ledger ‘0L’ in General Ledger Accounting. The ledger group which we assign to master area must contain leading ledger. In the same way we will specify ledger group ‘X1’ for depreciation area 30 which we use for parallel valuation for Indian GAAP. The ledger group of the area for parallel valuation is not allowed to contain the leading ledger. Asset values in area 30 will be posted to Non-Leading ledger X1, as shown in the below screen:

Posting control in depreciation area 30 should be set as “Area posts Depreciation Only”.

We do not have to set up a separate set of GL accounts for this new depreciation areas 30. Instead we use the same set of GL accounts of the master depreciation area 01. In this scenario, we do not have to create any new GL accounts in the chart of accounts or in the company code. We also do not have to create a new financial statement version for different parallel valuations and Ledgers. Depreciation area 30 uses the GL account set of depreciation area 01. Ledger group ‘X1’ is not allowed to contain the leading ledger when we specify X1 as target ledger group in depreciation area.

To enable this setting, we have to select 1 in the field “Different Depreciation Area” in depreciation area 30 as shown in the above picture.

2. Setup areas for parallel valuation

Using this wizard, system automatically creates a derived depreciation area that is used for updating the APC differences in the ledger group of parallel valuation. Posting control in the derived depreciation area is set as "Area posts only APC directly" while the real depreciation area for parallel valuation posts only depreciation.

Real depreciation area 30 for parallel valuation use the GL accounts of the master depreciation area 01 for posting values. If the accounts of the master depreciation area are entered as cost elements, then this also applies to parallel valuation, although there is no update to CO in this general ledger.

Follow the steps below:

Click on "Continue" button.

Enter the real depreciation area 30 for parallel valuation and target ledger group X1 and click on "Continue" button.

Since we have not created any derived or delta depreciation area in chart of depreciation ALTM for company code AIPL, here we will select option “Create New Depreciation Area” so that system  automatically creates the delta depreciation area for parallel valuation. System shows the difference between local and parallel valuation in this area and posts these differences in the ledger group for parallel valuation i.e. X1.

Click on "Continue" button.

Click on "Continue" button.

Click on "Continue" button and complete the setting.

Now see the depreciation area overview (Transaction code OADB)

Notice that ledger group X1 has assigned in both depreciation area 30, which is for parallel valuation and depreciation area 55 which is delta depreciation area for area 30 to post the difference between area 1 and 30.

3. Determine Depreciation Areas in the Asset Class

In this IMG activity, we determine the depreciation terms that are used in asset classes.

Select asset class 3000 ‘furniture and fittings’ and double click on “Depreciation areas” in dialog structure:

Deselect the check box ‘deactivate’ for depreciation area 30 so that all the depreciation areas will appear when we create an asset master under this asset class.

We have specified useful life 2 years for area 01 and 4 years for area 30.

4. Integration with the General Ledger

In this IMG activity, we specify the balance sheet accounts and the depreciation accounts for master depreciation area 01 and parallel depreciation area 30. For derived depreciation area 55, account assignment is not required.

Assign balance sheet GL accounts to depreciation area 1 as follows:

Similarly assign balance sheet GL accounts to depreciation area 30 and then assign depreciation GL accounts for depreciation area 1 and 30 as follows:

Depreciation area 1:

Depreciation area 30:

5. Specify Document Type for Periodic Posting of Asset Values

In this IMG activity, we specify a default document type for periodic posting of asset balance sheet values (values other than depreciation). This document type is used only by the periodic posting program, RAPERB2000. We have created a separate document type ‘SX’ for this purpose, the same will assign to company code AIPL in this step as follows:

We have completed the necessary configuration steps for parallel ledgers in asset accounting. Now we will test the same settings for the business scenario in the following steps:

6. Scenario for parallel ledgers

Create an asset master for ‘Furniture’ with straight-line depreciation method with the following parameter controls:

Depreciation calculation for asset value 2, 40,000/- for each depreciation area is as under:

Now, do the asset acquisition for above asset and then run depreciation for one period and finally retirement of the asset and see the effect in parallel ledgers.

7. Create asset master

Create an asset master for furniture.

Click on “Deprec.Area” tab page and give useful life and depreciatoin key are 1 and 30 as follows:

Now save the data, system has created asset master number 300011 for furniture.

8. Asset acquisition

Do asset purchase on date 01.03.2013 for amount 240,000 using following menu path or transaction code:

Asset purchase document has posted as shown in above screen shot.

9. Display asset value in asset explorer

Use the following menu path or transaction code to display the asset value for all depreciation areas for the asset posted in earlier step:

In the above screenshot, we can see the value in depreciation area 01 (Leading ledger valuation in local currency).

Now see the comparison value of depreciation area 30 as follows:

In the above picture, for depreciation area 30 (Non-Leading ledger valuation in local currency), system shows comparisons for four years (2013, 2014, 2015 & 2016) because we have given useful life four years in asset master 300011 for this depreciation area.

Note: System also shows value 10, 000 in fifth year i.e. 2017 this is because we have done asset acquisition in third period of the current year 2013 so in current year system could calculate depreciation only for 10 months and for remaining 2 periods, depreciation will be posted in year 2017 (5, 000 x 2 = 10,000).

Now display the comparison value of delta depreciation area 55. Here we can see that system shows the difference value between area 01 and 30 under depreciation area 55.

Example: For the year 2013, ordinary depreciation is 1, 00,000 in depreciation area 01 and for area 30 ordinary depreciation is 50, 000 in the same year so difference 50,000 (area 01minus area30) has shown under delta area 55. See the below picture:

10. Display Asset APC general ledger line items

The asset acquisition posting which is made in the leading ledger is automatically posted into the non-leading ledger also. Display G/L line items for asset ‘Furniture’ APC account for ledger 01 and 30 and notice that system has updated the same value in both the ledgers.

Choose ledger ‘X1’ by clicking on "Choose Ledger" button.

Execute and see the balance:

Now choose ledger ‘0L’ by clicking on "Choose Ledger" buttonand execute:

11. Run periodic asset depreciation

When we run depreciation program using below menu path or transaction code, system posts separate documents in each ledgers i.e. ledger ‘0L’ and ledger ‘X1’ with their respective depreciation amount according to depreciation key assigned in asset master data for each depreciation area.

First execute test run and then update run as follows:

Execute:

Notice that system has created two separate depreciation documents with different values for each depreciation area i.e. area 1 and area 30. Since area 1 is assigned to ledger ‘0L’ and area 30 is assigned to ledger ‘X1’ in customizing so system will post separate depreciation values to each ledger.

12.      Display depreciation GL line items

Display “book depreciation G/L account” line items for the each ledger using following menu path or transaction code:

Display balance for Leading Ledger – 0L

Display balance for Non-Leading Ledger –X1

Notice that system has posted depreciation value 10,000 for ledger "0L" and 5,000 for ledger "X1"

Thus depreciation amount of 10, 000 under US GAAP is posted in leading ledger ‘0L’ and the depreciation amount of 5, 000 under Indian GAAP is posted in non-leading ledger ‘X1’

13.      Asset retirement postings

We will retire the asset through sale for a value of Rs.2, 33,000 so that in US GAAP depreciation area, there will be a gain of Rs.3, 000. On the other hand, there will be a loss of Rs. 2, 000 in the Indian GAAP. The following are the accounting entries which should be updated in each ledger:

But when we do retirement postings in SAP, system does not post the separate values to each ledger i.e. 0L and X1 as explained in the above example rather the entries made in the leading ledger is duplicated in the non-leading ledger. In this case, system will pass the following entry in area 30 (Ledger X1) which is the same accounting entry updated in area 01 (Ledger 0L):

Due to this posting in Indian GAAP area, we can see the following mismatches in Indian GAAP ledger X1:

1. The reverse of accumulated depreciation is more by 5,000 because 10,000 has been reversed instead of 5,000
2. There is no posting for actual loss of 2,000 in this ledger

  3. Instead a gain of 3,000 has been posted.

To correct all these mismatches, the system automatically posts the entries necessary to reflect the correct position in Indian GAAP (Ledger X1) when we run the periodic asset posting program. This adjustment is done using the Delta depreciation area.

The following entry will be passed for adjustment using periodic program run:

Lets see replicate the above scenario in SAP using the following menu path or transaction code to do asset retirement posting:

Click on "Simulate" button.

Post the document:

Note: Line item 2 is for accumulated depreciation account in the above screenshot.

Display asset values in asset explorer for each depreciation area after retirement as shown below:

Depreciation Area 01:

Display Depreciation Area 30:

Display delta depreciation area 55:

Now display balance for G/L account 30000004 (Profits on asset disposal / sale) after doing asset retirement and notice that system has posted the same value to both ledger i.e. 0l and X1:

Transaction code: FAGLL03

Display balance for ledger X1:

In the above two screenshots, we can see that system has updated same value in both ledgers.

Now we need to correct these values and post the adjustment entry in non-leading ledgers using asset periodic posting as explained earlier in the example, use the following menu path or transaction code:

14. Periodic posting from fixed assets

We use this step to post the adjustment entries to specific ledger since we cannot post directly to reconciliation G/L. As per the retirement adjustment posting, we need to post to accumulated depreciation G/L account also which is reconciliation account.

Give the asset number 300011 in initial screen for which we want to post the adjustment entry.

First execute in test mode and then execute update run as follows:

In the above screenshot, we can see that system posts this adjustment document to ledger group X1 only. When we execute the update run, system creates the following document as per accounting entry explained in the example:

Note: Line item 3 is for accumulated depreciation account in the above screenshot.

Now after posting this adjustment document through periodic run, display balance for ledger account 30000004 (Profit on disposal / sale of fixed assets) for Ledger – X1 and notice that system has posted one reverse entry for the amount 3,000 which was posted during asset retirement:

This way system nullifies the balance of “Profit on sale” account for ledger X1 and posts to “Loss on sale” account, see the below picture:

Finally, after completing the above steps, we will find the GL balances for each ledger as per the accounting entries given in the example as mentioned below:

=====================================================================================

Thanks for your valuable feedback, advice and suggestions.

Please correct me if I have missed out something

Best Regards,

Ram Kumar Swami

1) 1221693 - FC: Consolidation fails with error ORA-01652 

2) 1222141 - ActivePDF and Finance Web Printing 

3) 1221716 - FC: ORA-03113: end of file on communication channel

4) 1909245 - FC10: Supportability with SAP Business Intelligence Platform 4.1 and SAP Information Platform Services 4.1 

5) 1221483 - FC: What is the difference between UTC, CET, CEST and GMT?

6) 1233860 - ORA-00955 "Name is already used by existing object" 

7) 1772120 - BOFC:Warning HRESULT E_FAIL has been returned from a call to a COM component 

8) 1829430 - FC Web Service Connection Test Error - SAP Financial Information Management 10.0 

9) 1809042 - FIM: What is the list ECC datasources supported by default with FIM?

10) 1775908 - ERROR: Server myCMSServer:6400 not found or server may be down (FWM 01003) - Financial Information Management (FIM) 

Be sure to check out the  Top 10 BFC-Suite viewed SAP Notes for April 2014  for the SAP Financial Consolidation Suite!

Hi

1.   Hi

      I am sharing the TAN exemption Process in vendor master after implementing the SAP Note 1975137

      1. Maintain TAX exemption detail in Vendor changes                                              Tcode : FK02

Purpose :

Maintain amount based accumulation in CIN details TAN exemption tab for both Invoice time and payment time tax type tax code.

Trigger  : Update Tax Exemption detail in the vendor master

Prerequisite : Create a vendor first than add W/H tax type and tax code in the vendor master

1.    2. Maintain table for mapping the W/H tax Type and codes                                 TCode : SE16

Purpose

Map the Invoice time tax type tax code with Payment time tax type tax code in View ‘V_FIWTIN_TDS_MAP’.

Note:

·         Do not activate the standard accumulation functionality in your withholding tax type if you are using TAN based accumulation.

·         Multiple exemption certificates can be maintained for the same tax type but the Exemption from date should be different

1.   3. Invoice Booking                                                                                                         Tcode FB60

Purpose :

Invoice booking against the vendor 

Prerequisite :

Create a vendor code and update the withholding tax type and code in the withholding tax tab and save it and update the TAX exempted section ,

dates , rates and value in TAN Exemption Tab in CIN

Business Process :

SCENARIO: 1

Amount Less then Equal to one lac for rent @ 22% on base value include 52% on TAN Exemption for  Rs.100000 as W/H threshold Amount

·         For section code 1004 : : “ xxxxxxxxxxxxxxxI”

·         W/H Tax Type RI : Sec 194I Rent Invoice

·         W/H Tax Code R1 - Sec 194I Rent Invoice - CO  @ 22% for rent

·         TAX Exemption 52%  on W/H threshold Amount 100000/-

SCENARIO: 2

Amount  More than one lac for Profession fess  @ 22% on base value include 52% on TAN Exemption for  Rs.100000 as W/H threshold Amount

·         For section code 1000 : : “xxxxxxxxx”

·         W/H Tax Type P1 :  Sec 194J Fees Professional/Technical Inv

·         W/H Tax Code P1 - Sec 194J  Invoice – CO @ 22 %

·         TAX Exemption 52%  on W/H threshold Amount 200000/-

SCENARIO: 3

Amount Less then Equal to one lac for Profession fess  @ 5.5% on base value include 50% on TAN Exemption for  Rs.100000 as W/H threshold Amount

·         For section code 1000 : : “xxxxxxxxxxxI”

·         W/H Tax Type P1 :  Sec 194J Fees Professional/Technical Inv

·         W/H Tax Code P1 - Sec 194J  Invoice – CO @ 5.5 %

·         TAX Exemption 50%  on W/H threshold Amount 100000/-

SCENARIO: 4

Amount  More than one lac for Profession fess  @ 5.5% on base value include 50% on TAN Exemption for  Rs.100000 as W/H threshold Amount

·                     For section code 1000 : : “xxxxxxxxxxxxxx”

·                     W/H Tax Type P1 :  Sec 194J Fees Professional/Technical Inv

·                     W/H Tax Code P1 - Sec 194J  Invoice – CO @ 5.5 %

·                     TAX Exemption 50%  on W/H threshold Amount 100000/-

SCENARIO: 5

Tax Calculation after expire of Validation date given in the TAN Exemption screen from 01.04.2014 to 30.06.2014. Less than one lac as this scenario working fine for Professional Fess  @ 5.5%

Thanks

Trinath

Introduction:

Purpose of internal control

Some companies are facing challenge to implement an internal control system.

Big companies listed on a stock exchange are forced by law to implement a system of

Internal control and risk management, SAP GRC Solution might be a good and valueable choice.

Small or medium sized companies who are not willing to implement a SAP module at the moment, but also want to have some kind of internal control can use SAP AIS for this purpose. (Business and System Audit)

To have some kind of automatism they can combine SAP AIS with SAP closing cockpit

Implementation of internal control with SAP AIS and SAP Closing Cockpit:

1. Entering SAP AIS menu:

Select: other menu and enter (as instance) *SAP*Auditor

Select SAP composite role

SAP AUDITOR is the “master role”  there are many roles available for special purpose like:

SAP Auditor for AR, FA or TAX. When you choose one of these roles the menu has

only functions concerning TAX or FA.

SAP AIS module is available

In this menu you will find hundreds of functions for control. One main advantage is,

that SAP provides all these functions in ONE menu

The menu also has some main topics like:

Making System Audit: Checks concerning security

Business Audit: Checks concerning financial reporting

1. Using SAP Closing Cockpit:

You can use SAP Closing Cockpit to run functions automatically.

From SAP EHP6 an additional task for internal control is available

1. Building a Risk and Control Matrix in Excel

You can set up risk and control matrix as an instance for:

Fixed Assets, Accounts Receivables/Payables, General Ledger, Bank Accounting

Your Risk and control matrics might look like this example:

First column: Target

Second column: Risk

Third column: Cecking  activity

Fourth Column: How control activity it is supported by SAP AIS

In the SAP AIS menu you also can find a lot of folders named CONTROLS.

Let yourself be inspired from these control routines, and use it for your risk and control

matrics

Example for control routine

Target: Check if posting have been made promptly and accurate time.

Risk: Postings have not been made contemporary, and might have some bad impact on

Quality of financial reporting

Checking activity: Using function S_ALR_87100998, here you have 3 statistical reports and 4

ranking reports.

Documentation:

Yes, this is not SAP GRC, so you have to make documentation manually.

In my opinion, it is possible setting up some kind of robust internal control system by combining

SAP AIS + SAP Financial Closing Cockpit.

Thank you for your valuable feedback,advice and discussion.

All the best

Erwin

Further information:

Find presentation about SAP AIS on SAP Service Marketplace.

Configuring the Interest Calculations Procedure

This configuration allows you to charge interest on overdue customer accounts.  Interest can be calculated by using the line items or overall account balances. SAP keep tracks of the date of the last interest run and stores it in the customer master record.

First create an Interest Indicator.

• OB46 - Interest Settlement Calculation Type
  Int Calc. Type
  P - calculate interest based on line items.
  S - calculate interest based on account balances.

  Secornd, make it avaliable to the interest run program.

• OB82 - Interest Terms

Third, determine the interest rate that will be used by the calculation.

• OBAC - Define Reference Interest Rates
• OB83 - Enter the Reference Interest Rates Value

  Fourth, assign the interest indicator to the reference interest rate.

• OB81 - Define Time Dependent Terms

Finally, determine the how and to which accounts the interest program will post.

• OBV1 - Prepare Interest on Arrears Calculation

Thanks

Chandan Bhatnagar

Step-1

OB57- Assign users tolerance group.

Here we are creating a blank tolerance group which is assigned to userid. However at step no: 2 (Tolerance group for users) can created as 'abc' and that can be assigned to the step no:1.

`

Step-2

OBA4 –FI Tolerance group for users

Amount per document  determines that the user has a privilege to  post a transaction  maximum up to the specified amount per document/invoice. Amount per open item pertains only to Customer/Vendor line items (F-43,F-22) and not to G/L line items (F-02) Percentage specified in Cash discount field determines the upper limit of  discount which user is authorized to process.

This permitted payment difference apply to the open item managed g/l clearing account and during Customer/Vendor payment clearing.  During clearing process system considers  which ever is the lowest whether the specified amount or the percentage.

Cash discount adjusted field applies during customer/vendor payment clearing. Amount specified in cash discount adjustment will add to the already existing discount conditions. If the payment received is less than the supposed amount and if the difference is not more than the amount specified in this field, system consider this as additional discount and it will reflect in the g/l assigned for discount loss/gain.

Step-3

OBA0-Tolerance for groups of G/L account in local currency

Here tolerance for groups of G/L account purely for open item managed g/l clearing account. eg; GR/IR,payable a/c, other clearing a/c which you want to clear manually or automatically.During clearing process system considers  which ever is the lowest whether the specified amount or the percentage. Also system consider the lowest amount from both the conditions specified in oba4 and oba0.

Step-4

FS00 –Create following GL account.

Cash and Rent payable accounts are created as open item.

Step-5

Assign GL Tolerance group to the open item managed account.

Here we are assigning the tolerance group created (step-03) to open item g/l account.So this account will behave according to the condition specified.

Step-6

OBXZ-Maintain FI configuration: Automatic Posting –Accounts.

During the clearing process (F-03) the clearing differences will hit the gain and loss account specified here.

Step-7

F-02- Enter GL Account Posting-1

In the first posting above the clearing account is credited for 1000 and in the next transaction below the clearing account is debited for 950 and due to that a difference of 50 arises. Since 50 is equal or less than the tolerance amount specified in both G/L and user tolerance, it's eligible to get cleared. However if it was more than 50, then system will throw error and won't clear during F-03. Also it must be noted that clearing amount must meet both user and g/l tolerance condition to get cleared.

Step-8

F-02- Enter GL Account Posting-2

Step-9

FBL3N-G/L Account Line item display-Open items.RED

These two line items are from the previous two postings, which are not cleared and status is red.

Step-10

F-03 –Clear GL Account

Here the open item managed g/l account need to be specified for clearing process.

Step-11

Click Process open items and follow the next screen below

Here the clearing difference is 50.00 which is 5% according to the condition specified in oba0 and oba4.Save it and the document will get posted in Company code AA

Step-12

FB03-Display posted document.

Tolerance gain amount got posted to the appropriate g/l account assigned in obxz.

Step-13

FBL3N-G/L Account Line item display- Select Cleared items.

Both the line items from Step-9 with status red is displayed here as cleared along with the clearing difference specified in oba0 and oba4.

Hope this will be useful.

Regards,

Sam

Hello Friends,

Lots of time I searched into the forum regarding the Customer/Vendor/General Ledger Line Items balance upload but I didn't got a satisfactory answer and nor I got the complete document to understand how the process of BAPI will work in LSMW.

Every time we need to go for BDC to upload our Line items of Customer/Vendor / General Ledger.

Today I am going to create the complete process of General Ledger Line items upload via LSMW BAPI ( BAPI_ACC_GL_POSTING_POST).

T.code -  LSMW

Now click on Setting- IDOC Inbound Processing or CTRL+ SHIFT +F1

Now on Next Screen Fill the Three Fields (File Port, Partn. Type, Partner No. )

Note:-  This naming convention can be different in other systems.

Now click on Activate IDOC Inbound Processing

Now click on YES and once you get the Message  "Data Saved", then come back or press F3 to proceed to main screen.  Below is the shot.

Now click on Execute or Press F8 to run the LSMW

Step 1. Maintain Object Attributes

Click on Save and come back

Step 2. Maintain Source Structures -  Here we need to create the structures based on the BAPI.  Here we are using the Business Object BUS6300 which belongs to Functional Module ( BAPI_ACC_GL_POSTING_POST ).

Below is the screenshot for your ready reference.

In the BAPI of G/L, We are having 3 Stages

1. 1.  Document Header
2. 2.  Line Items
3. 3.  Currency (Amount)

So I am going to Create three structure in LSMW.

Click on Save and come back

Step 3-  Maintain Source Fields -   Here we need to maintain the source fields which is available in the BAPI.  We can find the list of Fields which comes up automatically by clicking on "Object Overview", Below is the screenshot.

Copy all the field onto Excel File, as it becomes easy for you at the time of Field Assignment.  Below is my excel sheet screenshot for your reference

Do the same for Item & Currency Field as well.

Now will move back again to LSMW and do the field assignment.

Click on Save and Come back.

Step 4-  Maintain Structural Relations:-  Here we will maintain the relationship between the Header, Line Item & Currency.

Now click on Fisrt Item (Currently Blue in Colour) and then click on "Relationship"

Now link the three one by one in a sequence.  Below is the screenshot.

Then save and come back

Step 5;- Maintain Field Mapping and Conversion Rules

Now click on Extra ---->  Auto Field Mapping or CTRL + SHIFT + F3

Click Ok.

Mapping has been done correctly.  Save and Come back.

Step 6; - Specify Files- Here we need to maintain the Three File structure for Header, Line Item & Currency (As per the BAPI)

Do the same process for all the 3 Files (Header, Line Item & Currency)

also change the name of Imported Data and Converted data to anything,  else system sometimes gives the error due to this naming convention.

Click on Save & Continue.

Step 7:- Assign Files

Now again click on HEADERDATABAPI and click on Assignment and do the same for other two as well.

Click on Save and Back.

Step 7:-  Read Data

Come back to main screen

Step 8:- Display Read Data

Step 9:-  Convert Data - Select the only option "Create File" and execute

Step 10:- Display Converted Data

Step 11:-  Start IDOC Generation

Step 12:-  Start IDoc Processing

Click on Execute

Step 13:- Create IDoc Overview- 

Kindly Review the attachment file31 & 32.

To see the Documents go to T.code FB03 & See the entries ( Kindly see the Attache File 33. PNG for your ready reference)

Now after all these steps we can see that the process has been completely done and without any issues.

In this document I tried to explain the process from very basic point of view.

I would also request you all to let me know if you need any help on this from my side.

Thank you all for your valuable support.

Regards,

Pankaj Rana