cancel
Showing results for 
Search instead for 
Did you mean: 

Replenishment order

Former Member
0 Kudos

Hi Everyone

I try to setup the SMI scenario and it seems to work, but now i want to use the replenishment order, i am so far that i can create a replenishment order in SNC but it is not visible in ECC i assumed that it will create a PO in backend?

The replenishment order are asking me about a PO number in SNC, where do i get this number from, I would assume that this PO number should be initiated from ECC, but how and why do SNC not trying to send anything out of SNC.

we are using SCM 7.01

Best regards

Jakob Bang

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

I am new to SNC , can any one tell me the table names used to store replenishment data and also any BAPI or BADI to fetch the replenishment order details.

Please reply ASAP.

Thanks,

AB

Former Member
0 Kudos

Hi Jakob,

Maintain below settings:

You need to maintained same number range in ECC & SNC for SMI document type(if you have not created document type then u need to create document for SNC)

Refer below help link to create number range in SNC:

http://help.sap.com/saphelp_snc700_ehp02/helpdata/en/6b/9430405fa9e801e10000000a155106/frameset.htm

In master data for Vendor check Oder entry by vendor should be checked.

Maintain WVM7 setting

Maintain Partner data setting in We20

refer below links for more details

http://scn.sap.com/thread/1824469

http://scn.sap.com/thread/2066004

http://scn.sap.com/thread/1888259

Regards,

Nikhil

Former Member
0 Kudos

Hi Nikhil

sorry for the long waiting time, i have struggling a lot with our PI team.

but now next issue occur, when i create a RO in SNC then 2 different idoc are created, but the PO are still not created?

i have maintained

WVM7

following partner profiles are created in our ECC

message type     process code

ORDRSP            ORDR          

ORDRSP            ORDS

PORDCH            BAPI

ALEAUD            AUD1

DESADV            DELS

what i can see is that the PO number are genereted in SNC, but the PO are not created in ECC, we have also created a new numberrange and a new document type for the PO.

I can see in the blog that i must create message type ORDRSP process code ORDS.

it was also mentioned that we need following (VendorGeneratedOrderNotification) is converted into Idoc ORDRSP.ORDERS0 in R/3?, but there was no ORDERS0, so i guessed that the basis type must be ORDERS05.

can you advice what else to do

Regrads

Jakob

Former Member
0 Kudos

Hi Jakob,

Correct IDoc is Basic type ORDERS05 & message type ORDRSP

Can you check what error you are getting for above Idoc.

Regards,

Nikhil

Former Member
0 Kudos

Hi Nikhil

I actually got 2 Idoc's

1. ORDRSP / ORDERS05 Purchasing document 6100000030 does not exist

2. PORDCH / PORDCH02 ***** Messages for input and outbound processing *****

I have no idee why i got the second one.

BR

Jakob

Former Member
0 Kudos

Hi Jakob,

1. ORDRSP / ORDERS05 Purchasing document 6100000030 does not exist

May be in WVM7 purchasing document type you have maintain is having different number range that of  what you have maintained in SNC.

Can u check that.

Regards,

Nikhil

Former Member
0 Kudos

Hi Nikhil

I just checked the number range in ECC and the number range are

6100000000 - 6199999999 / ext number

the setting in WVM7 are as follow

Vendor - 626709

Cust.(sold-to party) - IBX CPH

Cust. (ship-to party) - IBX CPH

Purch. Organization - 2500  

Purch. Group              K17   

Plant                     2501  

Purchasing Doc. Type      ZSMI  

So one question could be, is it allowed to use a customer which is not a number?, it works perfect in SNC but what about ECC and does this customer need to be created in ECC?

Former Member
0 Kudos

HI Jakob,

Can you check the IDoc segement field LIFNR.

Go to IDoc >>E1EDKA1>>LIFNR

I think it will be 0000626709 where as you have 626709.

This may be the reason why system is not able to pick the setting from WVM7.

For test purpose you can change this data and reprocess the IDoc

Go to Tcode:We19 and change the value then reprocess inbound IDoc.

Regards,

Nikhil

Former Member
0 Kudos

Hi

I checked it and the Idoc are containing the correct data

LIFNR - 0000626709

this is the content of the Idoc

EDIDC   2000000000018333704731 51        2SAPQ3A    LSQ3ACLNT800

        E1EDK01
        E1EDK03                     01220131002132607
        E1EDKA1                     AG IBX CPH          0000626709
        E1EDKA1                     WE 2501             0000626709
        E1EDK02                     0016100000031
        E1EDK02                     002122
        E1EDK02                     0585700000039
        E1EDP01                     00001      1.0            PCE

            E1EDP02                     0016100000031                         00001
            E1EDP02                     0585700000039                         000008
            E1EDP20                     1.0                           20131031000000
            E1EDPA1                     WE 2501             0000626709
            E1EDP19                     0020313651-2
            E1EDP19                     0010313651-2

BR

Jakob

Former Member
0 Kudos

Hi Jakob,

That's why Idoc is getting failed.

In WVM7 you have vendor as 626709.

Can you replace 0000626709 with 626709 and reprocess the IDoc.

Regards,

Nikhil

Former Member
0 Kudos

Hi

good proposal, but unfortunately this didnt solve the issue, i tried to add leading 0 but they disapeared and the result was the same.

i tried to remove the leading 0 in the Idoc, then a PO was created but with the normal PO number (42XXX)

So i think we are on the right way. Do you know if we can force WVM7 to show leading 0?

/Jakob

Former Member
0 Kudos

Hi

Sorry, my mistake, the PO was NOT created, it was one of my colleauge who did a normal test at the same time.

still failing

/Jakob

Former Member
0 Kudos

Hi Nikhil

I found that when i try to modify in WE19 the Idoc was using ORDRSP / ORDR and not ORDS as you might remember we have both in WE20.

I tried to remove the ORDR and replace it with ORDS, this helped but gave a new error.

error message: IDoc does not have required type (ORDRSP VMI)

I though that was the ORDS?

/Jakob

Former Member
0 Kudos

Jakob,

In Inbound Partner Profile maintain the follwoing values:

Message Type : ORDRSP

Message Variant : SMI

Basic Type : ORDERS05

Process Code : ORDS

And then retest.

Regards,

Bharath

former_member183249
Active Participant
0 Kudos

Hi Jakob/All,

In Inbound partner profile you need to maintain the following values:

Message Type : ORDRSP

Message Variant : SMI

Basic Type : ORDERS05

Process Code : ORDS

In addition to this we need to pass " MESCOD = SMI" under  EDIDC40 segment of the IDoc (which is nothing but message variant) in the message mapping.

Once you do it you need to check the checkbox in the Idoc receiver channel "Apply Control Record Values from payload."

Once you will check it your Idoc will be processed successfully.

Regards,

Rahul