MBST and V_LIKP_VST

[Former Member]

Hi all,

We have encountered a problem with transaction MBST.

The transaction is being used to reverse an STO based on a PO. When attempting to cancel the document, the user is being presented with a "No authorisation to Shipping Point [Sending Shipping Point]".

SAP note 35902 is very similar to this - but only applies to VL07 and MIGO (and this form is not used in MBST).

Could anyone advise me on why this check is being made (and whether it can be safely deactivated)?

Thanks!

David

[Former Member]

Hi David,

Please let us know the outcome of your SAP interrogation- interested to hear the explanation for not including MBST in the previous SAP note 35902?

Good Luck Ol' Chap.......

Thanks

Dean

Edited by: Dean Platt on Jan 30, 2009 3:46 PM

Edited by: Dean Platt on Jan 30, 2009 3:48 PM

[Former Member]

Hi all,

Some more information:-

Investigation to date:

u2022 Authorisation value VSTEL is checked from structure LIKP in BERECHTIGUNG_PRUEFEN

o LIKP contains the header for the Outbound Delivery Note

u2022 SAP Note 35902 relates to similar issues for MIGO, MB0A and VL07 on the same form u2013 but doesnu2019t include MBST

u2022 SAP Note 1135737 does not seem to apply as the corrected code has not been accessed during Debug analysis

Version Details: SAP_APPL 500 0015 SAPKH50015 Logistics and Accounting

TABLE CALL STACK

9 SAPMV50A FORM BERECHTIGUNG_PRUEFEN

8 SAPMV50A FORM BELEG_LESEN_BUFFERED

7 SAPMV50A FORM BELEG_LESEN

6 SAPLV50S FUNCTION SD_DELIVERY_UPDATE_1

5 SAPLV50L FUNCTION SD_DELIVERY_UPDATE

4 SAPLV02V FUNCTION SD_DELIVERY_WE_FLOW_UPDATE

3 SAPMM07M FORM BUCHEN_AUSFUEHREN

2 SAPMM07M FORM FCODE_BEARBEITEN

1 SAPMM07M MODULE (PAI) FCODE_BEARBEITEN

Thanks in advance all,

David

[Former Member]

david,

i think this authority check is correct when you use MBST on a STO-scenario where you have either inbound or outbound deliveries. with reversing the incoming good-movement you are - in a way - reversing the process to 'the other side' of your STO-scenario.

can you please ask your funkies, whether it is imperative to use transaction MBST ... would another transaction do? could you please provide information whether your are using inbound/outbound deliveries?

[Former Member]

Hi Mylene,

Many thanks - it was because the funkies suggested that it shouldn't be checked that prompted me to ask the group.

As this check is excluded with MIGO, we have been able to use this as a workaround - however, I think it would be nice to know whether this check is meant to be made (by your argument, yes, it should, and hence why it was not removed). I welcome anyone elses' thoughts

Many thanks,

David

[Former Member]

there is an error in my thoughts. STO does not necessarily mean two plants on the same system. i neglected this, so i revoke everything i said before ) you cannot check a shipping point on another system, no sense in that, so yes it should have gone from MBST as it did from MIGO.

maybe SAP does not develop MBST any further, since we now all have MIGO? why not open an OSS-call and ask SAP herself??

[Former Member]

Hi Mylene,

Many thanks for your response - very helpful. We will look at raising a SAP message to ask them to confirm this.

Regards,

David