Skip to Content
0

S/4 HANA Sales Order 3rd Party using different ship to party & sold to party causing error in MIGO

Aug 25, 2017 at 02:35 AM

157

avatar image
Former Member

Hi All,

Kindly advice on this. This happen in SAP on premises 1610.

I have a cases in Sales order for 3rd party scenarios where by the sold to party and ship to party is different number. When i post in MIGO then it gave me error messages of "Inconsistency between a document field and the prof. segment number . Message no. KE396".

I've performed steps below but the error still existed.

To regenerate this program, call up function module 'RKE_GENERATE_INTERFACE_ACT' in the test environment and start it for the respective operating concern.

Example: If the name of the operating concern is 'S001', then regenerate program RK2LS001. Steps for generating the program RK2LS001:

1. Call up Transaction SE37 (Function Library: Initial Screen).

2. Enter function module: 'RKE_GENERATE_INTERFACE_ACT'.

3. Choose 'Sngl.test' (F8).

4. Enter import parameter ERKRS = 'S001'.

5. Choose 'Execute' (F8).

Also in Tcode: KEDR, it does not have sold to party and ship to party information.

Below is the screen shot of the error messages.

Thanks

Best regards

Khor

ke396.jpg (139.7 kB)
so.jpg (28.4 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Jürgen L
Aug 25, 2017 at 06:12 AM
0

Please follow the instruction of OSS note 321725 - KE396 f. charact. 'Customer' in third-party trnsctn

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Jürgen,

I've tried to perform the steps in OSS note 321725 but the error still existed.

Thanks.

Best regards,

Khor

0
Former Member
Former Member

Hi Jurgen,

I just found another OSS note:

2492776 - S/4 HANA Finance: Wrong customer in account-based line items for goods receipt in third-party direct ship (TPDS) scenario.

Let me try first.

Thanks.

Best regards,

Khor

0
Former Member
Former Member

After we implemented OSS#2492776 then the issues is solved.

0