Scribd
Upload
6 views9 pages

Process Subcontracting

Uploaded by

sandeep sandy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views9 pages

Process Subcontracting

Uploaded by

sandeep sandy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Set up new subcontracting location in APO SNP

1. Input checks
 Check with EIM team if the inforecord exists in WPP
 Any Key User of Service CL APO APC DP-SNP can request this.
 No further approvals are required

2. Add vendor to integration model variant


Transaction CFM1, variant APC_SNP_MD_VD
If the RDC is on SAPFIL then the subcontracting vendor also needs to be added to the
SAPFIL vendor integration model. If the RDC is on DAPSAP then the DAPSAP vendor
integration model needs to be updated.

Add the vendor to the list of existing vendors and save the variant. (Do not overwrite the
list of vendors in the variant!)
Then activate the integration model (transaction CFM3, variant APC_SNP_MD_VD)
3. Check if vendor exists in APO

Transaction /SAPAPO/LOC3
Enter four zeros preceding the R3 vendornr and check if it exists in APO:

In the “Addit.” Tab of the vendor master, enter the location type as “OEM”.
4. Create subcontracting location

Transaction /SAPAPO/LOC3

Enter RDC location + ‘_’ + vendor location, fill in location type 1050 and click create.

In the next screen, enter the location description. Fill in assigned plant as the RDC
location, and assigned vendor as the vendor location (don’t forget the leading zeros!).
Go to the next tab, fill in mandatory field Country. Leave the other fields blank and save.

Assign the new location to model 000:


Press ‘assign model’, then select model 000, then press the left ‘box’ button, press the
continue button.
5. Create means of transports

Create MOT from RDC to subcontractor to supply finished products. No products should
be added.

Flag the ‘all products’ indicator on the MOT

Create MOT from subcontractor RDC to supply combi’s. No products should be added.

Flag the ‘all products’ indicator on the MOT


6. Add vendor to purchase inforecord integration model
Only after preceding steps have been taken should you add the vendor to the PIR
integration model

Transaction CFM1, variant APC_SNP_MD_PI


Add the vendor to the list, save the variant and activate the integration model.

When this integration model is activated the combi’s will be added to the transportation
lane from subcontractor to RDC automatically.

7.
Add RDC to subcontracting PDS integration model

Transaction CFM1, variant APC_SNP_MD_PDS


Add the RDC to the list of locations, save the variant and activate the integration model.

After this integration model has been activated it will automatically add the components
of the combi’s to the transportationlane from RDC to subcontractor in APO.
8. Check in APO if all masterdata is ciffed correctly

 PDS-es should exist for subcontracting location.


 Product specific transportation lanes should exist to and from subcontracting
location.

Checks if it doesn’t work:


 Combi and component should be apo relevant
 BOM should exist, status active and in validity dates
 Production version 1000 should exist for correct BOM type, and be checked
(green indicator)
 Purchase inforecord should exist for correct vendor, and refer to production
version 1000

R/3 team Activities:

Further R3 settings based on onekernel sapfil RDC:


To have the complete picture for the APO relevant combi's I will mention all the APO
relevant (combi) material related masterdata that have to be maintained in SAP:
Header Material (SAP Material type COMB) MM01
(MM02)
 Basic Data 1:
- fill the Ext. Matl. Grp with the combi code. Send an email to MDO
(Jose Mulschlegel) to request that she adds the combi description
to the CTV description.
 MRP1 view:
- MRP type ‘Z0’
- MRP controller ‘001’
- Lotsize ‘EX’)
 MRP2 view:
- Procurement type ‘F
- Special Procurement ‘30’
- SchedMarginKey ‘000’
- Planned Delivery Time ‘# days between PO creation and receipt of
finished combi’
 MRP3 view:
- Strategy Group ‘10’
- Consumption mode ‘3’
- Fwd Consumption ‘14’,
Bill of Material (BOM) CS01
(CS02)
 Selection screen:
- Combi code
- Plant where the combi is produced and delivered from
- BOM usage ‘5’
 Enter all component 11NC’s and quantities that are in the combi
 and
 Selection screen:
- Combi code
- Plant where the combi is produced and delivered from
- BOM usage ‘1'
 Enter the same component 11NC's and quantities as in BoM usage 5 + if
necessary and an agreed way of working with the service provider also
other components necessary for production;
Production Version C223
 Selection criteria:
- Plant,
 On a new line, fill
- Material ‘combi code’
- Production Version ‘1000’
- a description of the production version;
- Valid From ‘today or at least should fall within the validity period
of the BoM’,
- Valid To ’31-12-9999’
- From lot size: '1'
- To Lot size: '999999'
- BOM usage ‘1’;
Then select the line for which the production version should be checked (the ones
with a yellow traffic button) and press 'consistency check' button (the scale) at the
bottom of the screen
Purchasing Info Record ME11
 Selection screen:
- Vendor ‘subcontractor number'
- Material ‘combi code'
- Purchasing org. ordering the combi’
- Plant where the combi is created’
- Info category 'subcontracting'
 Press Button ‘Purch. Org. Data 1’
- Planned delivery time ‘# days between PO creation and receipt of
finished combi’
- Production Version ‘1000’,
- Purch. Group '000'
- Net Price (if required by the system): 1 EURO per Piece (if this
field is not required or if it is greyed out you do not have to enter a
price);

You might also like