Message_type_x short dump (MB_POST_GOODS_MOVEMENT)

[Former Member]

We have encountered program termination (message_type_x short dump) in our customized program that's using BAPI_GOODSMVT_CREATE.

Short dump details:

Error analysis

Short text of error message:

No authorization for maintaining sales documents in P001 01 00

Long text of error message:

Diagnosis

According to the settings in your user master record you do not

have the authorization to execute this function.

Procedure

If you need this authorization, contact the person responsible for

assigning authorizations.

Authorization object: V_VBAK_VKO

Technical information about the message:

Message class....... "V1"

Number.............. 515

Variable 1.......... "P001"

Variable 2.......... 01

Variable 3.......... 00

Variable 4.......... " "

Source code in which the program terminated:

CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'

EXCEPTIONS

error_message = 4.

• As soon as we have started to put things into UPDATE TASK, we must

• ensure that errors definitely terminate the transaction.

• MESSAGE A is not sufficient because it can be catched from

• external callers which COMMIT WORK afterwards, resulting in

• incomplete updates. Read note 385830 for the full story.

IF NOT sy-subrc IS INITIAL.

MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH "385830

sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

• MESSAGE A263.

ENDIF.

Although the program terminated, the transacted data were posted in the tables.

Is this authorization issue or patch-gui issue?

Need some help in analyzing what caused the short dump.

regards,

Aida

[Former Member]

Hi aida,

I suggest you review the role and profile (Tx SU01) of the user executing the transaction to avoid problems with authorization. The user must have authorization for maintaining sales documents.

Hope this information is help to you.

Regards,

José

[raymond_giuseppi]

Look if

- material document is posted

- sales order is updated

Regards,

Raymond

[Former Member]

Yes, the material document was posted. But there is a short dump encountered. I want to know what could possibly caused the termination.

Thanks and regards,

Aida

[raymond_giuseppi]

The system try to update a sales order document (related to the goods movement) and user seems

not to be allowed to the sales organization P001.

SU21 - V_VBAK_VKO is "Billing: Authorization for Sales Organizations" and check activity vs Sales organization

In error message - dump

- VKORG Sales organization is P001

- TWEG Distribution channel is 01

- SPART Division is 00

Regards,

Raymond

[former_member404244]

Hi,

it seems some authorization issue..user is not allowed to the sales organization P001. Try to create manually and see.

Regards,

Nagaraj

[Former Member]

Hello Raymond,

So it's really possible that even if the user has authorization issue that might caused the dump, the goods movement will still be posted?...

Thanks and regards,

Aida

[Former Member]

Hi Aida,

First try to check if the user have proper autorizations or not.

you can do this by recreating te entire scenario. after you encounter short dump, execute the SU51. there you can find if user is missing some roles.

If user is missing then you can request basis to add roles to that user id.

Porpbaly the user might be haing partial autorization to post the material document and he may not have autorizations to update the sales document for the company code you specified.

Thanks

Kiran

Edited by: kiran Pasala on Sep 24, 2009 5:08 AM

[raymond_giuseppi]

This message should have been an A-Abend message to rollback update of data, but the commentary suggests that SAP got some problems with it and convert it to a X-dump message, first try to find and apply any available notes in OSS for your version of SAP. (check the program names in the stack in the dump to find notes)

Start with those old notes (sample)

- [Note 385830 - Inconsistencies with goods movements in the background|https://service.sap.com/sap/support/notes/385830]

- [Note 556000 - Short dump due to note 385830|https://service.sap.com/sap/support/notes/556000]

Regards,

Raymond