FOR OLD ORDERS SHIP TO, SOLD TO ARE NOT APPEARING

[Former Member]

Hi All,

I am getting a problem that old orders which are created say one month back, sold to party and ship to party are disappeared, when I go to display/change mode system asking to enter sold to party(but actually they are created successfully),

For some customer in the same account group (0001) this error occurs and for some customers with same account group (0001) itu2019s going smooth.

To test them for the same customers I created new orders with same data, and I check in change and display modes this time ship to and sold to be appears.

.

[Jelena]

My guess is that there has been a configuration change (in Partner Determination Procedure?) that negatively affected the existing documents. Check the old records against the new records directly in the database (SE16) and see what fields are different. This should provide a clue. The tables to check are VBAK, VBAP, VBPA.

[Former Member]

Hi What actually happening is,for orders which are missing sold to party i entered manually sold to and ship to in va02 ,but i check in partner functions at header level ,there is no sold to party in partner functions ,i found only ship to, and bill to ,and payer

(sold to party is missing here itsely so it is not updated in VBPA table)

so what can do to get sold to party in to partner functions ( account group is 0001).

[Former Member]

Hello Colleague;

To hide the sold-to and ship-to parties in a particular sales order,

goto VOV8 and select the sales order type and assign 'NO_VARIANT' to

sales order type.Now,create the transaction variant in SHD0 and you can

see the results by testing the variant.There are some restrictions to

variants.Variants are able to operate on screens in SAPMV45A program

only.For further details,please check the point 7 note

582767 which address for pricing details. Maybe this procedure could be done times ago.

7. Question: Which restrictions apply to the dynamic transaction

variants in the sales order?

This function is only implemented for screens in the SAPMV45A program.

For example, not on the condition screen, pricing screen and text

screen.

Furthermore, you cannot change the initial screen of the create

transaction (VA01, for example) because the order type is not known at

this time.

Also, you cannot manipulate both menu options and function codes.

If you require both, you only have the option to use a variant

transaction or to implement a source code modification in MV45AFZZ FORM

USEREXIT_FIELD_MODIFICATION.

I hope it can be interesting for you

regards

Ruy Castro