Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 10548

Re: New SNC PROACT scenario

$
0
0

The PI system place data in receiver system,  in a RFC queue.

 

After RFC queue data, input is stripped from XML  and placed in a nice SAP table structure=/SCA/BIF_MD_PROACT_NOTIF

 

The receiver system should have structure=/SCA/BIF_MD_PROACT_NOTIF regenarated after PI-system have made the his changes.  This knows all PI persons all about.


Goto into receiver system SCM system, in SE80 and chose display "enterprise services browser"
browse to "SNC 7.01", it is the service for the SCM system,
chose "Service interfaces"
CHOSE "ProductActivityNotification_In"
LOOK IN Provider Class        /SCA/CL_BIF_PROACT_IN
fIRST STATEMENT IN METHOD IS:  "ls_input = input". IT IS THE MULTI-LEVEL ABAp TABLE,
IT IS THE RESULT AFTER THE xml-input HAS BEEN STRIPPED, BY THE SERVICE/SYSTEM CLASSES,
FROM HERE IT IS JUST TO FIND SOME badi'S

Debug would be a good idea, be aware he is running with background user "PI_RFC" in our case.

You could also use the SM50 eternal loop trick.

Or be logged on as PI_rfc user

 

 

tECHNICAL NOTES:
Use these 2 BADI's
Badi= /SCA/BIF_I_PROACT method=AFTER_CONVERSION
BADI= /SCA/TS_EXCEPT method=TS_EXCEP
first BADI, Add new input tables, to timeseries-table
Second BADI, New timeseries-table are given a new key

 

It is a little clumpsy, but in the input there is no code field telling us something about the content,

so we have to recognize via the "TAG" name.

 

Hope these princips it helps


Viewing all articles
Browse latest Browse all 10548

Trending Articles