New_IC_Billing_Process_set_up (123).pptx

Maintenance of table ZINFS5_ICBIL_DEV via SE38

Maintenance of partner profiles via WE20

Maintenance of SD number ranges for outbound IC invoices

Maintenance of FI number ranges for outbound IC invoices

Maintenance of FI number ranges for inbound IC invoices

Maintenance of output condition records for ZD04 via VV31

Creation of listing for ZIC0 via VB01

Adjustment of IC_BILLING variant for RBDAPP01 via SE38

Adjustment of IC BILLING variant for ZINF_IC_PDF_INVOICEFB03 via SE38

1. 1 New Inter-Company Billing Process Issuing company Receiving company Intercompany sales order creation Type ZICO / ZDCI Recording cost elements of invoice recipient IC partners and IC products Outbound Intercompany invoice - Type ZICI / ZICC (cancellation ZC04 / ZC05) - Output via IDoc Inbound Intercompany vendor invoice - Automatic vendor invoice posting via Idoc - Outbound pdf invoice is attached to the inbound invoice (via batch-job RBDAPP01_IC_BILLING every 30 minutes) New IC process can be used via SAP standard transaction VA01 or via sales cockpit (ZSD_SALES1) New sales order type ZICO for debits and ZDCI for credits Enhancement enables the recording of the cost element (cost center or WBS element) of the invoice recipient already in the sales order New IC invoice types ZICI for debits (with cancellation invoice type ZC04) and ZICC for credits (with cancellation invoice type ZC05) IC outbound invoice triggers an IDoc (electronic document) which is automatically processed via a batch-job at the invoice recipient and which creates the inbound IC invoice (using SAP transaction FB01) Finally the outbound pdf invoice is linked to the inbound IC invoice via a batch-job (RBDAPP01_IC_BILLING)

2. New Inter-Company Billing Process 2 The purpose of this document is to describe the necessary set up steps whenever a new company has to be activated for the new IC billing process. The whole IC billing process from the end-user perspective is described here:

3. New Inter-Company Billing Process Set up Activities 3 EDI settings: The main activities are in the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI: Mapping of partner addresses via WEL1

4. New Inter-Company Billing Process Set up Activities 4 Maintenance of table ZINFS5_ICBIL_DEV via SE38 Maintenance of partner profiles via WE20 Maintenance of SD number ranges for outbound IC invoices Maintenance of FI number ranges for outbound IC invoices Maintenance of FI number ranges for inbound IC invoices Maintenance of output condition records for ZD04 via VV31 Creation of listing for ZIC0 via VB01 Adjustment of IC_BILLING variant for RBDAPP01 via SE38 Adjustment of IC BILLING variant for ZINF_IC_PDF_INVOICEFB03 via SE38

5. New Inter-Company Billing Process Set up Activities 5 - Bullet points 2 and 3 are linked to the usual SAP transport system. Settings have to be done in E1D and have to be transported to E1Q and E1P afterwards. - All other bullet points have to be done manually in each system (normally in E1Q and E1P). - Settings under bullet point 1 described in the slides 10 and 12 should be done via SE16N in change mode for an easier and significant faster maintenance of the tables T076I and T076K. To insert new entries whenever there is a new company which should be activated for the IC billing process the following excel file can be used as a template to prepare and copy the needed entries into T076I and T076K. - Settings under bullet points 6 and 7 have to be checked during the usual year-end activities and potentially extended for the next year(s).

6. New Inter-Company Billing Process #1: EDI Settings 6 Follow the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI  Enter Program Parameters for EDI Incoming Invoice This IMG activity defines the main parameters and the way the inbound invoices will be created. The parameters are e.g.: the postings keys the document types for invoices and credit memos whether the invoice will be parked or posted directly through … In principle we are using currently the following alternatives how to post inbound invoices: 1.1 Inbound invoices will be park or not 1.2 Jurisdiction code will be transferred or not

7. New Inter-Company Billing Process #1: EDI Settings 7 1.1 Parking of invoices or direct posting For two receiving companies we park the invoices. These are 9604 and 9628: So for any sender of an invoice the flag ‘Park document’ is set whenever 9604 or 9628 is the receiver of an IC invoice. For all other receivers the flag is not set. Such parked invoices have to be transferred manually to Accounting in 9604 and 9628.

8. New Inter-Company Billing Process #1: EDI Settings 8 1.2 Transfer of jurisdiction code The two Chinese entities (9700 and 9705) are charging always 6,72% tax for non-domestic IC business. This tax is non deductible at the receiver’s side and is posted with a special tax key (usually K1; see also slide …). Whenever a US company is the receiver of such an invoice we need to post these inbound invoices with jurisdiction code. To enable this the flag ‘Tax jur.code transf.’ must be set:

9. New Inter-Company Billing Process #1: EDI Settings 9 Follow the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI  Assign Company Code for EDI Incoming Invoice With this IMG activity each EDI partner is assigned to the company code (that contains the payable to be posted) to the name for the invoice recipient in the EDI invoice. Example for partner 43000:

10. New Inter-Company Billing Process #1: EDI Settings (Table T076I) 10 Follow the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI  Assign G/L Accounts for EDI Procedure For each EDI partner and invoice company code (company code for the vendor) the G/L account is assigned to. Actually we have a one-to-one mapping of the 18 IC materials to a cost account at the receiver’s side. Example for LI + 43000 + 4380 with details for IC material F7080110010: The whole mapping table for IC material to cost account can be found in the end-user documentation (see slide 2) on page 4.

11. New Inter-Company Billing Process #1: EDI Settings 11 Follow the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI  Assign Tax Codes for EDI Procedure For each EDI partner the outgoing tax codes / tax rates are mapped to the inbound tax code by receiving country. Example for LI + 96030: For country US the mapping is blank except for the two Chinese entities (LI = 97000 and LI = 97050) where the non-deductible outbound tax is mapped to K1.

12. New Inter-Company Billing Process #1: EDI Settings (Table T076K) 12 Follow the IMG under Financial Accounting (New)  Accounts Receivable and Accounts Payable  Business Transactions  Incoming Invoices/Credit Memos  EDI  Assign Additional Account Assignments for EDI Procedure For each EDI partner an assignment to a cost object ( cost center, WBS element, …) at the receiver’s side can be done. Due to the fact that we are using a user-exit to derive the cost object from E1EDP30 segment with either qualifier 045 (for cost center) or 047 (for WBS element) no assignment is done. Example for LI = 43000 and company code 4380:

13. New Inter-Company Billing Process #2: WEL1 13 Transaction WEL1 is used to link logical addresses of sender and receiver of an IC invoice within the SAP system. An entr y in WEL consists of: Logical address: Company code of the receiver of the IC invoice Account number (10 digits) of the sender of the IC invoice Destination: Company code of the sender of the invoice Account number (10 digits) of the receiver of the IC invoice With details:

14. New Inter-Company Billing Process #3: Table ZINFS5_ICBIL_DEV 14 The own-defined table ZINFS5_ICBIL_DEV is used to activate a sales organization for the new IC billing process. Besides the sales organizationthe table contains a validity date: The validity date defines the date the new IC process is activated. That means all IC sales order / IC credit memos created for that sales organization on or later that date are using the IC enhancement (e.g. additional data B on item data is now available to record the receiver’s cost center / WBS element).

15. New Inter-Company Billing Process #4: WE20 15 The SAP standard transaction WE20 is used to define the partner profiles (outbound and inbound) which will be used for EDI communication. For each company two entries have to be made. One for partner type KU, one for partner type LI. Example for outbound parameters of partner type KU: With details: Outbound Idocs will be processed immediately.

16. New Inter-Company Billing Process #4: WE20 16 Example for in bound parameters of partner type LI: With details: Inbound Idocs will be processed by background program (see slides 24 and 25)

17. New Inter-Company Billing Process #5: SD number ranges for outbound IC invoices 17 SD number ranges for outbound invoices are maintained via ZSD_CUSTO: The SD number ranges are depending on company code and billing type: ZICC: ZICI: ZC04: ZC05:

18. New Inter-Company Billing Process #6: FI number ranges for outbound IC invoices 18 FI document types DC and DD are allocated to SD billing types ZICI and ZICC (same FI document types DC and DD used for SD cancellations ZC04 / ZC05): FI document types DC and DD are using FI number ranges 71 and 70 (same for cancellations):

19. New Inter-Company Billing Process #6: FI number ranges for outbound IC invoices 19 FI number ranges can be maintained via SNUM for RF_BELEG or via the IMG Financial Accounting (New)  Financial Accounting Global Settings (New)  Document  Document Number Ranges  Documents in Entry View  Define Document Number Ranges for Entry View. Example for the number ranges 70 and 71 for company code 4300:

20. New Inter-Company Billing Process #7: FI number ranges for inbound IC invoices 20 FI document type KC is used for inbound invoices (see also settings on slides 5 to 7). FI document type KC is using FI number range 93 (same for cancellations):

21. New Inter-Company Billing Process #7: FI number ranges for inbound IC invoices 21 FI number ranges can be maintained via SNUM for RF_BELEG or via the IMG Financial Accounting (New)  Financial Accounting Global Settings (New)  Document  Document Number Ranges  Documents in Entry View  Define Document Number Ranges for Entry View. Example for the number range 93 for company code 4300:

22. New Inter-Company Billing Process #8: Output records for ZD04 22 The invoice message type ZD04 is used to generate an Idoc in the outbound IC invoice. Condition records are maintained via VV31. For each sales org. activated for the new IC billing process the following conditions records exist (example for 4380):

23. New Inter-Company Billing Process #9: Listings for IC Materials 23 The listing is used to ensure that only defined IC materials can be used in the IC billing process for IC customers. Listing is maintained via VB01 for listing type ZIC0: Example for an existing listing (customer 43800):

24. New Inter-Company Billing Process #10: IC_BILLING variant for RBDAPP01 24 The inbound processing of INVOIC Idocs is set to ‘trigger by background program’ (see slide 16). Hence the INVOIC Idocs have to be processed by SAP standard program RBDAPP01 with variant IC_BILLING:

25. New Inter-Company Billing Process #10: IC_BILLING variant for RBDAPP01 25 Whenever there is a new company which needs to be activated for the IC billing process this company has to be included in variant IC_BILLING as a new sender:

26. New Inter-Company Billing Process #11: IC BILLING variant for ZINF_IC_PDF_INVOICEFB03 26 The own developed program ZINF_IC_PDF_INVOICEFB03 is used to attach an outbound IC pdf invoice to the inbound invoice at the receiver’s side. Variant IC BILLING is used:

27. New Inter-Company Billing Process #11: IC BILLING variant for ZINF_IC_PDF_INVOICEFB03 27 Whenever there is a new company which needs to be activated for the IC billing process this company has to be included in variant IC BILLING as a new sender to ensure the automatic attachment of outbound IC pdf invoices of this company to inbound invoices: