cancel
Showing results for 
Search instead for 
Did you mean: 

SHPMNT05 idoc (message type SHPMT) failing

Former Member
0 Kudos

Hi,

We have  an inbound SHPMNT05 idoc coming into ECC . I need to know whether in standard SAP, this inbound idoc creates shipment document  in ECC or it just changes an existing shipment document already created  in ECC

1 ) In my current inbound idoc, we have E1EDT20-TKNUM=23456  and E1EDT18=ORI.    TKNUM is shipment number

That means will this idoc  create a shipment document  in ECC with shipment number = 23456  . Am I correct ? If yes, then I think we need to have an external number range for shipments ? we do not have any shipment number 23456  existing in ECC currently.

2) the above inbound idoc is also failing. The message is "transportation planning point  2000 does not exist " . We do not have 2000 as tranportation planning point configured in system. The issue is there is no segment in idoc which carries tranportation planning point.  i checked in WE 60 idoc documentation too, there is no segment for transportation planning point for this idoc  . So   why is idoc failing The idoc carries the delivery number and the company code of sales order is 5600. for this company code, there are many transportation planning points in config except 2000 ?

regards

Pamela

Accepted Solutions (0)

Answers (2)

Answers (2)

neeraj_lal
Contributor
0 Kudos

Pamela Pilch

I will suggest you to execute this Idoc in test mode (WE19) in forground. This is really helpful.

Looks like inbound Idoc do not have correct date.

1.  Yes, you are right TKNUM indicates Shipment number

2. For Transportation planninning point 2000, check below thread.  This has details of ow to fill Transportation planning point in shpmnt05 Idoc type.

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

Regards

former_member186385
Active Contributor
0 Kudos

Hi Pamela,

yes, you are correct. Inbound idoc SHPMNT05 is used to create Shipment documents,

can you check the assigned function module for this idoc whether any customized code has been put to call the external number range?

May be in SNRO any new object might have created to trigger external number

regards,

santosh