on 10-28-2014 10:25 AM
Hi,
We are mapping SMI with replenishment order scenario. We are using SNC 7.02 with service pack11
After Replenishment order creation in SNC, we are able to create PO in SNC but it is not getting created in ECC.
We are getting below issues.
1. Purchasing Document 20000000015 does not exist.
2. No Function Module for input process code ORDS
3. EDI: Partner Profile inbound not available
Regards,
Laxman
Hi Laxman,
Have you created RO with reference to contract?
It seems RO is created without valid contract.
If this is the case then:
You need to CIF the contract from ECC to SNC.
Once you CIF the contract then transportation lane in SNC will be created automatically.(transaction code: /N/SAPAPO/SCC_TL1)
Enter model=000,Start location=Supplier location,Dest.location=plant.
Check here transportation lane is created with contract here.
Also create means of transport here.
then try to create RO and check.(also ensure you have maintained setting in transaction code: WVM7 in ECC)
Regards,
Nikhil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil,
I have created RO with reference to valid contract.
Tlane is available with this contract no.
Have maintained below settings also.
1. Vendor master check Order entry by vendor
2. WVW7 settings. with same number range for PO in SNC and ECC for Document type, external
3. Partner profile : Message type ORDRSP, Process Code ORDS, Message Variant SMI
Problem is Process Code ORDS is not having any Function module or Workflow
So now we have maintained ORDV as process code in partner setting still PO is not getting created in ECC.
In We02 having message 62 - IDoc Inbound Procg: Work item 00000169xxx started
Regards,
Laxman
Hi Nikhil,
Error was - No function module for input process code ORDS.
We found out that work flow component for process code ORDS is missing
So we maintained ORDV as process code which is having same work flow component - WS20000183
And when we debugged FM(VMI_PO_CREATE_FROM_ORDRSP_VMI) we came to know that segment - E1EDK14 is missing in inbound IDoc because of which PO is not getting created.
Plant - 7200, Plant BP - 7200, Supplier - SNP001, Supplier BP - SNP001
In WVM7,
Vendor - SNP001
cust (Sold-to-party) - 7200
Cust(Ship-to-party) - 7200
Purch, Org - SNC1
Puch. Grp - 001
Plant - 7200
Purchase Doc Type - ZSNC
And I have one question - Once this PO is created in ECC shd this created Auto confirmation to SNC ??
If Yes, then what are the settings to be done.
Thanks in advance
Regards,
Laxman
Hi Laxman,
And I have one question - Once this PO is created in ECC shd this created Auto confirmation to SNC ??
No there should not be any confirmation sent to SNC.
In WVM7 setting remove Cust(Ship-to-party) - 7200.
Check the business partner of the customer in the ORDSP IDoc(segement E1EDKA1 field PARTN)
Cust(Sold-to-party) should be same as value of the field PARTN.
Then reprocess the IDoc
Regards,
Nikhil
Hi Nikhil,
I changed the settings as you said
In E1EDKA1 AG - I am getting 0000007200
in E1EDKA1 WE - I am getting 7200
In AG I changed to 7200 and reprocessed the IDoc.
Now I am getting Status 62 - IDoc inbound Procg: work item 000000169118 started.
If auto confirmation is not coming back to SNC, then should supplier has to confirm the PO before doing ASN. Please suggest
Thanks
Regards,
Laxman
Hi Laxman,
In SMI scenario RO is created by supplier itself then why supplier will confirm again the same RO which was created by him.(in standard SAP integration it is not supported)
You can check SAP standard message flow:
Let me know for any further clarifications
Regards,
Nikhil
Hi Nikhil,
Now we are getting this message after using input process code ORDV
Status 62:
IDOC inbound procg: work item xxxxxxxxxx started. in inbound idoc
please suggest what next has to be done.
If we are using ORDS process code
we are getting: No function module for input process code ORDS.
Regards,
Laxman
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.