GOA not replicating to Back end & Diffe processing times for BLAORD&CONDA

[Former Member]

Hi All,

I have created a GOA and it does not repliacte in the Backend system.

On checking the RZ 20 I get the following details:

Back end system application error & Different Processing times defined for BLAORD &CONDA

Working with SRM 5.0.

Any inputs are appreciated please.

Thanks & Regards,

Nagarajan

[Former Member · Accepted solution]

Hi Nagarajan,

have a look into the Log (SLG2) in the backend. This error is the typical message connected to a missing mapping of conditions, a missing material information, etc.

- did you map conditions?

- do you get the error with a free text typed item as well?

- leave all conditions blank also price, does it then work?

Only when all information is valid in both systems, then a GOA gets distributed.

Look into the log and let know the messages there.

Cheers,

Claudia

[former_member183819 · Accepted solution]

Hi You can check it out this notes

646903-GOA Tips and tricks.

Muthu

[Former Member · Accepted solution]

Hi Claudia,

I could not find any logs in the Backend system using slg1/slg2.

Thanks ,

Nagarajan

[Former Member · Accepted solution]

Hi,

do you have an Idoc for the GOA in Backend? Check in trx WE02.

For a contract there should be an Inbound Idoc for BLAORD and one for COND_A. There is more information mentioned in the status. Check the status 51 and the information given.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi Claudia,

Thanks all of you for your efforts.

I could solve the issue and I could replicate the Contract into the Backend systems.

But the following are still bewildering:

1)Status of distribution in Header in WEb and Gui are still Incorrect

2)There is another associated Idoc getting generated in the Backend ( Out Box direction) going to error

due to message type EKSEKS (Purchasing Document data to Purchasing Info system).

I have not experienced this before.

How do I ensure that this is created by which Badi ie Badi BBP_CTR_BE_CREATE or Badi BBP_CTR?

Please provide inputs

Thanks & Regards,

Nagarajan

[Former Member · Accepted solution]

Hi,

are you able to call the contract in Backend via trx me33k? Only when the contract is visible there, the distribution worked. What doc type are you using for the GOA? Are all settings in parallel in place in SRM as well in R/3?

To which Idoc Type is the second message connected? I think it is not related to you issue.

Once again check trx WE02 for the status of the Idoc. I assume it is still red and has the status 51.

In order to get the conditions mapped you need to implemente R/3 Badi BBP_CTR.

Cheers,

Claudia

[Former Member · Accepted solution]

Hi Claudia,

Thanks for that.

I think the failed Idoc is not relevant so far as Distribution is concerned.

I am able to display teh Contract in the Backend in Tx Me33k.

Thanks all,

Regards,

Nagarajan

[Former Member]

Hi Nagarajan,

1. Please check whether the partner status in partner profiles is Active in backend system

2. Please make sure the message types BLAORD & COND_A have the inbound options. i.e. both should have the same status { "Trigger by background program" or "Trigger Immediately" }

Best Regards

Kathirvel

[former_member183819]

Hi Naga

The same problem reported in SDN

it might be useful for your quick diagnosis.

Edited by: muthuraman on Jul 28, 2008 3:10 PM

[Former Member]

Hi Muthu,

I checked the Link.

Not very useful for this error.

What exactly is meant by Processing times and where do we maintain this?

If Trigger immediately is what it means then it is maintained in the Partner profiles.

Thanks & Regards,

Nagarajan