cancel
Showing results for 
Search instead for 
Did you mean: 

PO output getting triggered sometimes but not everytime

former_member591501
Participant
0 Kudos

Hi Experts

We have come across an issue in which a customized PO message output is not getting triggered in some cases.

We have checked the condition records and did not find any discrepancy.

We also looked for any particular timings or trends but could not get anywhere.

Any suggests are welcome. Please advise.

Thanks

Harsh Aggarwal

Accepted Solutions (1)

Accepted Solutions (1)

former_member591501
Participant
0 Kudos

Hi All

Thanks for your responses.

I have created an OSS message and following up with SAP.

Thanks again

Harsh Aggarwal

Answers (6)

Answers (6)

Vinay-S
Explorer
0 Kudos

Hi Harsh,

I have similar issue for an EDI medium output type, can you please let me know the response from SAP ?

Thanks,

Vinay.

former_member591501
Participant
0 Kudos

SAP had requested for steps of replication which we could not provide as the issue is non-replicable. After some time this issue stopped happening so we stopped pursuing it.

former_member201529
Active Contributor
0 Kudos

Dear Harsh,

Kindly check the condition types are maintained in "Fine-Tuned Control: Purchase Order" in below path and try.

OLME - Messages - Output Control - Message Types - Define Message Types for Purchase Order - Fine-Tuned Control: Purchase Order.

Regards,

Karna J

former_member591501
Participant
0 Kudos

Hi

The issue is not resolved yet. We are still analyzing it. If there are any more pointers please share with me.

Former Member
0 Kudos

Hello,

Are you trying to trigger the output after the changes made to the PO or while creation, if you want it during the time of change, just want to make sure you have maintained the fine tune settings in your system.

Also make sure the Partner Profile(SAPGPQ110) is maintained in your system.

Thanks,

Manish

Former Member
0 Kudos

Hello,

If there is no log it can have one of those reasons:

- the message has been created manually

- no condition record existed

- no output device was found

- the message schema in customizing has been deactivated

Thanks,

Manish

former_member591501
Participant
0 Kudos

Hi Manish

Thanks for your response.

The output is not getting triggered at the time of PO create and not PO change.

Harsh

Former Member
0 Kudos

Hi Harsh,

Could you please check if you are getting the same message for successful hits as well or not. And if not kindly check the determination analysis over there.

I think if you are not able to see the analysis still, go back and check all your config settings again.

Thanks,

Manish

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi Harsh,

Please let us know the condition table for which you are expecting the output type to be triggered. Does the condition table contain any PO line item level field? Is the issue only for one condition table?

Thanks and Regards,

Yugank Arora

former_member591501
Participant
0 Kudos

Hi Yugank

We are using the condition table 26: Purchasing Output Determination: Document Type that does not have any line item level field.

Yes, the issue is only for one condition table as condition record is maintained only for this condition table.

Thanks

Harsh

Former Member
0 Kudos

Hello Harsh,

So, maybe you can post a screenshot from the determination analysis when the output is not triggered ...

Alexandre

former_member591501
Participant
0 Kudos

Hi Alexandre

Here is the screenshot, it does not show Determination analysis logs.

Former Member
0 Kudos

Hello Harsh,

Once, you are on the PO main screen, click on Messages. The output are displayed, from there, in the main menu, click on Goto and select "Determin. analysis".

This is the starting point for your investigation. The log displays per output type which conditions are triggered or ignored or found but not executed...

Additionally, I already came across an issue where an output with a custom condition table was not triggered in some situations and I had to move it up in the sequence sequence. This is managed under MM>Purchasing>Messages>Output Control :

Analyse the PO messages log, check your system configuration to determine how the settings are influencing the output control for the problematic message type.

Alexandre

former_member591501
Participant
0 Kudos

Hi Alexandra

Thanks for your response. I checked in the system and I could not find "determination analysis" in the purchase order. Is there a way to activate determination analysis? Also, we could not replicate the case in test system as the issue is intermittent.

I checked the message output configurations but did not find anything suspicious. Do you remember why you had to move the sequence of condition table in access sequence? when did your message output did not get triggered?

Hi Experts

Does anyone have any other suggestion?

Thanks

Harsh Aggarwal

RobynCouch
Contributor
0 Kudos

Hi Harsh

I've had similar issues and eventually traced it back to the PO partner determination.  It may not be what is causing your issue but make sure the PO partner used in your output conditions is always determined.

Keep in mind that the are three levels of PO partner and the sequence you enter data during PO creation can affect the results of PO partner determination.  We found it was possible for two identical PO's to have different partners simply because the data was entered into ME21N in a different sequence.

Regards

Robyn

Former Member
0 Kudos

Hello Harsh,


Let's consider the output type NEU from the screenshot in the previous post, inside the access sequence Z987, the determination is progressing through access number and in my case, the number 30 was always true so the number 40 was never executed.

So, I had to reorganize the order used to read the condition tables.

Otherwise for the determin. analysis :

1. On the PO click on message

2. On the next screen, select the message, in the the menu, select goto and determin analysis.

former_member591501
Participant
0 Kudos

Hi Alexandre

I am quite sure we do not have sequencing issue as most of the time condition record is picked up and output gets triggered.

Also, we do not see determination analysis logs in our system.

Thanks

Harsh Aggarwal

former_member591501
Participant
0 Kudos

Hi Robyn

Can you please elaborate here?

1. Is partner determination at PO level for vendor OR partner determination at message output level?

2. what are three levels of PO partner? different ways to enter it during PO creation.

Thanks

Harsh