define intercompany billing
DESCRIPTION
Define Intercompany BillingTRANSCRIPT
![Page 1: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/1.jpg)
1201 / Cross Company Sales Configuration
Monday, May 19, 200310:10 AM - 11:10 AMContent Area: Order
Management
Dave Hubert Molex
![Page 2: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/2.jpg)
Business Process Requirement
• Molex is a global implementation of SAP . Single shared instance used by sales org companies in 18 countries and 45 manufacturing/distribution centers.
• Customers want to order upon their local or regional sales org and receive shipments from any manufacturing plant eliminating buy-stock-resell.
![Page 3: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/3.jpg)
Process Example
• Customer places order to the North American sales organization.
• ATP requirement for delivery directly from a plant in Japan.
• North American company bills the end customer.
• Japan company bills the North American company and cost of sales , a/r , a/p , COPA and SIS/BW all reconcile.
![Page 4: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/4.jpg)
Demonstration
• R/3 system used is 46c support pack 40 in April , 2003.
WRF File
![Page 5: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/5.jpg)
Configuration Steps
• MM & SD master data• SD Billing and Pricing • PA Flow of Values• SIS/BW updating• FI AR/AP EDI• FI G/L master data and PCA rule• EDI partners• Process Trace Verification
![Page 6: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/6.jpg)
Define Account Groups for Internal Vendors and Customers With External Numbers
• For configuration in a development system , the customer and vendor number must match that of the production system.
• Use a consistent convention so that the same entity as a customer and vendor is easily recognized by the code. (I.E. V-xxxx or c-xxxx).
![Page 7: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/7.jpg)
Account Group Number Ranges
• Object ‘Debitor’ for customer. Use transaction XDN1 to create and assign a number range for an account group. OBD2 to create the customer account group.
• Object ‘Kreditor’ for vendor. Use OSMJ to define the range. XKN1 to create number range. OBAS to assign to the account group. OMSG to create the account group.
![Page 8: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/8.jpg)
Create the Customer and Vendor Masters in Development , QA and Production
• Do not define your vendors as plants so as to trigger stock transport order purchasing.
• Create all customers and vendors for all sales orgs and purchasing orgs with necessary company code views. XD01 for customer and XK01 for vendor.
• Indicate the customer number of the vendor in the vendor master and the vendor number in the customer master in change mode.
![Page 9: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/9.jpg)
Vendor Customer Association
![Page 10: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/10.jpg)
Define Intercompany Billing
• Define the sales area that represents the delivery plant – OVV9
• Define the customer that represents the sales organization of the order. (The sales org of the end customer order which will be the customer of the sales org of the delivery plant) – OVVA. Please note that because this uses an actual customer number , to do the maintenance in a development system with transport suggests the use of an external number for the account group and an intelligent convention.
![Page 11: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/11.jpg)
Typical Entries for Sales Org Customers
![Page 12: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/12.jpg)
Create a Special Billing Type for Intercompany Billing
• VOFA. You may want a separate type for cross company sales intercompany billing versus the intercompany billing of a stock transport order. This to derive different copy controls , SIS or BW update rules and especially the pricing procedure.
• Assign this type to the end customer order type – OVV8. Define copy control VBX2.
• Define background user authorization for this billing type plus global invoice entry!
![Page 13: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/13.jpg)
Define Pricing Procedure for Intercompany Billing
• Likely to be the similar to the end customer procedure with special intercompany conditions. SAP provides material specific price and percent condition. Some sites may always compensate as a percent of end customer revenue and some may have fixed price relationships. Only a condition type defined as intercompany will be calculated in an intercompany billing.
![Page 14: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/14.jpg)
Simple Pricing Procedure
![Page 15: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/15.jpg)
Billing Document Example
![Page 16: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/16.jpg)
Copy Control Using Origin Price If Desired
![Page 17: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/17.jpg)
Intercompany Pricing Conditions
• One entry for 2 separate conditions. First condition defined as the cost to the sales organization of the order. The second condition defined as the price from the sales org of the delivery plant.
• This facilitates the map to PA and the postings to SIS.
![Page 18: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/18.jpg)
Master Material Specific Condition
![Page 19: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/19.jpg)
Condition for Inter-co Cost
![Page 20: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/20.jpg)
Maintain the Intercompany Conditions – VK11
• No SAP authorization based upon sales org of order. No validation of material with sales org of order as a key. Only conditions using sales org perform these functions so access to the pi01, pi02 conditions requires procedural enforcement.
• Maintain the master condition and the reference condition will find the value.
![Page 21: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/21.jpg)
PA Postings
• Flow of value conditions in SD pricing of the billing document to Profitability Analysis determines whether a cost or revenue account is defined.
• This is why there are separate pricing conditions in the end customer billing document as a cost to the selling org and as a revenue condition in the billing document of the delivery org. Both derived from a common condition.
![Page 22: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/22.jpg)
Flow of Actual Values KE4I
![Page 23: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/23.jpg)
SIS/BW Postings in End Custoemr Pricing
![Page 24: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/24.jpg)
SIS Update Rule Interco
![Page 25: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/25.jpg)
SIS Update Rule Standard
![Page 26: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/26.jpg)
IMG – Inter-company Billing
![Page 27: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/27.jpg)
Define Intercompany Invoice Processing
• WEL1 – define the edi logical address.String entry with intelligence. The
first 4 positions are the characters of the company of the delivery plant. The rest of the entry is the customer number of the sales org of the order. Remember that company is a character field not a numeric field although numbers may be in the entry.
![Page 28: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/28.jpg)
WEL1 Entry
![Page 29: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/29.jpg)
Matching Companies to Vendor and Customer for Automated EDI Invoice
![Page 30: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/30.jpg)
Define Output Type – V/40
• Defined so as to create an idoc for internal edi posting upon billing document save.
• SAP has provided RD04 keyed by the sales org of the intercompany invoice (sales org of the delivery plant) and the customer bill to partner (customer representing the sales org of the order to the end customer).
![Page 31: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/31.jpg)
Output Type Settings
![Page 32: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/32.jpg)
Output Type Settings
![Page 33: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/33.jpg)
Maintain Output Determination
![Page 34: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/34.jpg)
Maintain Output Procedure for Billing – V/42
![Page 35: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/35.jpg)
Assign Output Procedure to Billing Type – V/25
![Page 36: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/36.jpg)
Create Output Condition Records – VV31
![Page 37: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/37.jpg)
FI Configuration for Incoming Invoice -OBCE, OBCC, OBCD,OBCB
![Page 38: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/38.jpg)
Posting Keys for Incoming Invoice by Vendor Per Company - OBCE
![Page 39: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/39.jpg)
OBCE Considerations
• Input tax field entry must be valid for this company.
• Standard unit of measure for common parts must default.
• Review by table t076s using se16.
![Page 40: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/40.jpg)
GL Accounts - OBCB
• Best to review by se16 for table t076i to audit the entries.
• Define a ‘cost of goods sold’ account for the posting of the incoming invoice derived from a sale to the end customer.
• Enter partner type LI , vendor account number , company code , * in goods and services.
• Enter g/l account and company code.
![Page 41: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/41.jpg)
OBCB Example
![Page 42: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/42.jpg)
Additional Accounts for EDI - OBCC
• Enter partner type LI.• Enter vendor number.• Enter company code.• Enter * for acct assignment id.• Review in table t076k.
![Page 43: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/43.jpg)
OBCC Example
![Page 44: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/44.jpg)
Tax Code Rates by Vendor and Arrival Country - OBCD
• Country is the country of the company of the sales org of the end customer order. The company receiving the intercompany invoice.
• Enter partner type LI , vendor account , tax type ‘vat’ , rate , country and tax code.
• Review in table T076M.
![Page 45: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/45.jpg)
OBCD Example
![Page 46: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/46.jpg)
Define the G/L Accounts and Reconciliation Accounts for Tax and Field Display – FSS2
• In tax category by account set * for tax category.
• Mark posting without tax allowed.• Make sure that the field status group
allows entry of the quantity and unit of measure fields. If not you may see some unusual messages saying that the fields are not in specific screens.
• One account is defined in OBCB , the other in the vendor master.
![Page 47: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/47.jpg)
Reconciliation Account for Vendor
![Page 48: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/48.jpg)
G/L Account Master Data
![Page 49: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/49.jpg)
Substitution for Profit Center Accounting
• If you do not want the profit center of the delivery plant to pass into the incoming mm invoice , an FI substitution rule can be used to default a relevant profit center for the company of the sales org of the order.
• Transaction OBBH substitution by company code. Prerequisite step:Document type = ‘**' AND G/L account = ‘******‘ as defined obce and obcb.
![Page 50: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/50.jpg)
Substitution Example
![Page 51: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/51.jpg)
Maintain the EDI Partner Profiles – WE20
• Vendor and Customer Partners must be maintained for special processing of message type ‘invoic’.
• If using a 46c release or later , do not follow standard SAP advice to use message code ‘FI’ as that is no longer usable with Logistics Invoice Verification.
![Page 52: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/52.jpg)
Vendor Example
![Page 53: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/53.jpg)
Vendor Example
Message code is blank with LIV
![Page 54: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/54.jpg)
Vendor Example
Agent for workflow review of idoc failure is at the company of the outbound SD intercompany billing document
![Page 55: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/55.jpg)
Customer Example
![Page 56: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/56.jpg)
Customer Example
Generic Port defined for edi or ale
![Page 57: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/57.jpg)
Customer Example
![Page 58: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/58.jpg)
Customer Example
![Page 59: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/59.jpg)
Customer Example
• The other tabs for customer are irrelevant• Post processor , edi standards , telephony.• Process code sd08 and necessary function
module is provided by SAP.
![Page 60: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/60.jpg)
Process Tracking
• Create the sales order process and post the normal customer invoice by the sales org of the order and then the intercompany invoice by the sales org of the delivery plant.
![Page 61: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/61.jpg)
Process Tracking
• Check the accounting document for the posting of the intercompany invoice.
![Page 62: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/62.jpg)
Process Tracking
• Note the header of the accounting document an the user.
![Page 63: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/63.jpg)
Process Tracking
• Go to the header output of the SD intercompany billing document.
• For the rd04 output type (or equivalent) , use the ‘processing log’ pushbutton.
• If the output type is shown with a green light , an idoc should have been created. Write down the idoc number.
![Page 64: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/64.jpg)
Process Tracking
![Page 65: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/65.jpg)
Process Tracking
• Go to WE05 to review the specific idoc. • Enter the idoc on the additional tab manually
(does not cut and paste)• Check the green or red status codes
![Page 66: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/66.jpg)
Process Tracking
• Double click on the message type ‘invoic’ to expand to detail .
• Expand the status records code 53 for a green light or 51 for a red light. If green , there should be a message listing an accounting document.
![Page 67: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/67.jpg)
Process Tracking
• Use fb03 to display the accounting document as an incoming invoice to the company of the sales org of the order.
![Page 68: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/68.jpg)
Process Tracking
• Note the header of the accounting document and the user.
![Page 69: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/69.jpg)
Reference Materials
• Service.sap.com white paper ‘Customizing Value Chain 9’ by Best Practices for mySAP Automotive.
• OSS notes 31126,137686,162990,308989• SAP release notes for 3.0A Intermediate
document structure ‘invoic01’.• SAP IMG help ‘Automatic posting to Vendor
Account (SAP-EDI)• Trial and Error.
![Page 70: Define Intercompany Billing](https://reader030.vdocuments.us/reader030/viewer/2022033005/55cf9cf4550346d033abaa47/html5/thumbnails/70.jpg)
Thank You for Attending!
Please Remember to Complete and Return Your Evaluation Form
Following This Session.
Session Code: [1201]