Procurement visbility scenario not working

[Former Member]

Hi,

We have integrated procurement visibility scenario but till now for PO created in ECC , no event handlers are getting created in EM.Following are the settings done:

From ECC side:

a) Activating the PI-EM using transaction BF-11

b) Define RFC to Call EM System using SM59

c) Define EM System

d) Activating Application Object Type and BPT and marked all event types as relevant

e) For Procurement Visibility Process the following Event Types is  activated:

 PCM10_ACKNWL (ESC_PURORD)

 PCM10_PO_CHANGE (ESC_PURORD)

 PCM10_ASN (BPT- ESC_DELIV)

 PCM10_INVOICE (BPT - ESC_MM_INVOICE)

 PCM10_PAYMENT(BPT- ESC_FI_CLEARING)

From EM side:

a) Define RFC to Call ECC System using SM59

b)  Define EM System

c) Assign Mapping Area

d) Assign Web Transaction to User

Currently no logs are available in SLG1.

[Former Member]

Hi Dipak,

Please attach your PO header and item from EKKO/EKPO and Application Object type screen shots. Then we can figure out the issue.

Thanks,

Vishnu

[Former Member]

Deepak,

1) Put a breakpoint in BADI(se19): /SAPTRX/MM_PURCHORD and see if it's calling FM:  /SAPTRX/EVENT_MGR_COMMUNICATE.

2) If std AO Type is used, put a break point in /SAPTRX/XRA_MM_ITEM_PCM10 and see if result = 'T'. If custom AO Type used, put breakpoint in relevant relevance.

3) Finally, put a breakpoint on SE38 = /SAPTRX/LASC2F01 in the form FORM post_tracking_object_data and see if it hits BAPI POST FM.

Let us know where you have issue here. If all is OK, then we can check EM.

Thanks,

Vishnu

[Former Member]

Also, check if you have maintained application system in tcode /SAPTRX/TSC0AS

Thanks,

Vishnu

[Former Member]

Aopplication system is maintained

[Former Member]

One quick question-

Since for the event types, ASN,Ackn,GR,IR we are using std extractors and these extractors have std values codes like for Porg-0001, document type NB etc. Does that mean that if I create PO with only these values then only my EH gets created or my EH gets created for any Porg values if we are using the std extractors

[Former Member]

Hi Dipak,

First of all, there are two types:

1) AO Type = Event Handler Creation

2) Event Type = Posting Events

1a) If you use standard relevance, your PO should have same values which is used in AOT relevance. Other wise it will be false and no EH is created.

2a) If you use standard relevance, your PO should have same values which is used in EVENT TYPE relevance. Other wise it will be false and no EVENTS will be created/posted.

send us AOT screen shots and if you can share, your sample PO EKKO/EKPO.

Thanks,

Vishnu

[Former Member]

Hi Dipak,

Yes these are created for SAP template and used for standard but we can customize on our own with referent to these.  If you have custom one then go to AOT and set EM Rel. Method - B Check Condition and maintain relevant condition config to check custom Pur.Org - 5001 or 3001 and PO Types 'ZNB or ZUB etc.

Execute same thing for Event Types as well.  Check and let me know.

Regards

GGOPII

[Former Member]

But I am little worried why for std values the procurement scenarios would come out with such error.I am using std Porg values-0001 AND DOCUMENT TYPE NB as per the code logic for EE extractor

[Former Member]

Hi Dipak,

1. Can you paste the screen shot of full SLG1 as I can't see on until last what happened?

2. Go to Application object type - PCM10_ITEM -> Event Mgmt. Relevance tab -> Check PCM10_ITEM maintained in EM Rel.Function and maintained EM Rel. Method - A Check Function.  Go to parameter setup and check TrkID Method - A Determine by Function and Trk. ID Extractor as - PCM10_ITEM.

3. Check your purchase order transaction satisfies below condition?

IF ( <ls_xekpo>-loekz <> 'L' AND
      <ls_xekko>-bsart = 'NB' AND
      <ls_xekko>-ekorg = '0001' AND
      <ls_xekpo>-pstyp = 0 AND -
      <ls_xekpo>-menge > 0 ) OR
    ( <ls_xekpo>-loekz <> 'L' AND
      <ls_xekko>-bsart = 'NB' AND
      <ls_xekko>-ekorg = '3000' AND
      <ls_xekpo>-pstyp = 0 AND
      <ls_xekpo>-menge > 0 ).

Regards

GGOPII

[Former Member]

Hi,

The issue is resolved by updating the logical system with new nomenclature.

However a new issue is coming up.In EH list, once we create PO and confirmation details are mainatined at item level, only receive Acknowledgement event is triggered whereas other events like ASN and GR events are not reported although inbound delivery and GR has been posted.I am pasting the screenshot of EH list and SLG1 log of the rule set:

Can the experts check this issue

[Former Member]

Hi Dipak,

As you can see from SLG1, the event condition failed. That means your event is not generated from Event Type ( if that's what you configured ).

Goto your BPT ( IMG->Integration->Event Management Interface->Define Application Interface->Define used Buss. Proc Types, AO Types & Event Types), select the event types and check the relevance conditions for these events. See if the relevance is True or False.

Did you use custom Event Types for BPT ESC_PURORD or using BPT ESC_DELIV for these events?

Thanks,

Vishnu

[Former Member]

Hi Dipak,

1. ASN and GR belongs to ESC_DELIV, Check event types PCM10_ASN and PCM10_GR are checked the box "EM Relevance of Event Type"

2. Go to event type PCM10_ASN Event Mgmt. Relevance table -> Relevance function check if EH exist -> Check the table /saptrx/aotref -> AOID in AOID field and check the data exist.

3. Event type PCM10_GR -> ensure that check box enabled in "EM Relevance of Event Type"

Regards

GGOPII

[Former Member]

Hi,

All the relevancies are marked here.Kindly check the ATTACHMENT .I am using only std events for PCM10.

[Former Member]

Scroll to your right and find the values in EMRelMeth, EMRelFunc, EMRelCond.

If using EMRelFunc, then paste the code here.

Did you copy these event types from ESC_DELIV?

Thanks,

Vishnu

[Former Member]

Hi Dipak,

You cannot use event types PCM10_ASN and PCM10_GR in Business Process Type ESC_PURORD because Evt Data Extractor and Event Management relevance function belongs to Business Process Type ESC_DELIV.

You just go ESC_DELIV and enable EM Relevance of Appl. Obj in both PCM10_ASN and PCM10_GR event types or you have code your own Evt. Data Extractor and Event Management relevant function to enable in ESC_PURORD.

Check this end to end configuration of Procure to Pay scenario in help.

Defining Application Object Types and Event Types - SAP Documentation

Check this discussion where we provided solution and it contains procurement visibility scenario configuration document.  You can configure as per configuration document.

Insufficient date/time information for event RE... | SCN

Regards

GGOPII

[Former Member]

Hi,

I have a quick question.

As per the config step 3, we need to select AOT- PCM10_ITEM and then under event types the respective values for PCM10_ACKNOLWL and PCM10_PO_CHANGE needs to be maintained.

However when we go to ESC_DELIV and ESC_MM_INVOICE there is no reference to proceed to AOT-PCM10_ITEM and then maintain corresponding event types but rather the config guide just says from BPT to go to event type without maintaining AOT which I feel is not correct.Can you comment on those .

In case AOT needs to be maintained for ESC_DELIV and ESC_MM_INVOICE , is the control table values same as PCM10_ACKNOLWL and PCM10_PO_CHANGE

[Former Member]

Hi Dipak,

It doesn't require AOT PCM10_ITEM for PCM10_ASN and PCM10_GR because event types reference tracking code set and tracking id to post event.

If you go to AOT PCM10_ITEM -> Parameter Setup -> Tr.ID Extractor  -PCM10_ITEM -> click Tracking ID functions -> you can see e_trackiddata-trxcod = 'PO_TECH'. 

PCM10_ASN -> General Data -> Evt Data Extractor PCM10_ASN -> Click function and you can see code ls_trackingheader-trxcod  = 'PO_TECH' that connects this event type.  Same code go to line item 137 ls_trackingheader-evtid   = 'RECEIVE_ASN' and it connects SAP EM expected event profile PCM10_ITEM to event ID RECEIVE_ASN.  Then post reported event in the system.

It is happening same for PCM10_GR but event id is different.

Configure as per document and let me know.

Regards

GGOPII

[Former Member]

Hi Dipak,

Have you entered SAP EM system below config?

SAP ECC:

1. Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types -> Define Used Business Process Types - > Event Manager - Select EM System which you configured.

2. Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types -> Define Event Types - > Event Manager - Select EM System which you configured.

3. Have you entered Event Mgmt. Relevance to trigger in AOT and Event Types?

SAP EM:

1. Maintain Application System in IMG- > Event Management -> Event Handlers and Event Handler Data -> Parameters -> Assign Profile to Mapping Area

Check and let me know.

Regards

GGOPII

[Former Member]

Yes all the above entries are maintained

[Former Member]

Hi Dipak,

1. Go to SE19 and enter /SAPTRX/MM_PURCHORD in Classic BADI -> Interface -> double click on Posted method.

2. Put the breakpoint in CALL FUNCTION 'GET_R3_EXTENSION_SWITCH' and CALL FUNCTION '/SAPTRX/EVENT_MGR_CHECK'

3. Now create PO and save.

4. It should stop at these call functions and proceed debugging to check the root cause.

Check and let me know.

Regards

GGOPII

[Former Member]

Hi,

I am attaching the SLG1 log and the event type config.Can you let me know if this error is the reason why no EH is created.If so what needs to eb done to resolve this issue.

[Former Member]

Hi Dipak,

This is Event Type for creating events. Unless you are creating EHs out of Event Messages via EM config, this will not tell why no EHs are getting created.

First check the AO Type relevance for the PO AO Type and see if it's true.

From your screen shot, goto "Define Application Object Types", select your ESC_PURORD and goto relevance tab, put a breakpoint at first executable line and check the result = 'T'.

In addition add SLG1 after PO create to see if PO EH is getting created or not.

Thanks,

Vishnu