Skip to Content
avatar image
Former Member

Account assignment messages: warning to error

Hi all,

We're on SRM Server 550, SP12 with R/3 4.7 backend in Classic scenario.

Accounting data is set to 'real-time backend validation'.

SAP standard account assignment checks appear as warnings in SRM transactions (e.g. BBPSC03). Examples:

W BBP_PD 822 Error in account assignment for item 1

W BBP_PD 047 System status CLSD is active (ORD 12345)

We need these messages to appear as errors.

My questions:

1. Is this a standard behaviour, or are we missing something (e.g. an SAP Note)?

2. Is there any solution available from Customizing perspective? Setting these to errors in "Influence Message Control" does not have any effect.

3. If the only option is custom development, which BAdI is more suitable:

- BBP_MESSAGES_BADI "Check of account assignment data and message output", or

- BBP_DOC_CHECK_BADI "General BAdI in Cross-Check for Message Returns"

Cheers,

Serguei

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Sep 03, 2008 at 06:09 PM

    Hi,

    These two messages appear as Error in our system in shopping cart application.

    E BBP_PD 822 Error in account assignment for item 1

    E BBP_PD 047 System status CLSD is active (ORD 12345)

    Hence please have at the "Message Control" to make sure that appropiate business objects have been added for these messages. Please have a look if there are any backend developments/configs maintained for the same.

    I would suggest BBP_DOC_CHECK_BADI for the same if things do not work out.

    Regards

    Kathirvel

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 05, 2008 at 07:35 PM

    Answering your findings:

    1. Yes, BBP_PD 047 and BBP_PD 822 are displayed as warning message in SRM per standard system design.

    2. Yes, since these messages can represent different kind of errors in SRM, coming from R/3 backend, the customizing "Influence Message Control" doesn't have effect in this case. A BADI would be a good solution.

    3. With the BBP_DOC_CHECK_BADI, you can check the accounting information and perform a strict accounting verification, performing an exception when necessary.

    Add comment
    10|10000 characters needed characters exceeded