on 2018 Feb 01 8:04 AM
Hi,
We want to read inactive entity data specific to a CR in USMD_RULE_SERVICE~CHECK_ENTITY and We have a parallel processing scenario as such:
There is a CR(#1) in progress for a Supplier BP, Purchasing Org and Company Code is extended in the CR but not yet activated. A new CR(#2) is created for the same BP and new purchasing org and company code is extended.
We use IF_USMD_MODEL_EXT~READ_CHAR_VALUE to read inactive data with readmode=gc_readmode_no_act(4) by specifying BP ID and CR number in IT_SEL. Although CR(#2) number is specified, the value returned are all the inactive data for the BP, instead of specific CR.
According to API guide https://www.sap.com/documents/2015/07/666e4158-5b7c-0010-82c7-eda71af511fa.html, usage of API is forbidden in Rule Service BAdI. However, we have tried to use IF_USMD_CONV_SOM_GOV_API~GET_CREQUEST_DATA, it did return the inactive data specific to the CR but it causes other issues related to entity mandatory check errors.
Any pointers how we can read inactive entity data specific to CR in Rule Service BAdI?
Hi all,
What I have done to resolve the issue of reading inactive entity data in Rule Service BAdI is by reading the Active data (readmode = no_inact) and Default data (readmode = default) first, and then filter off the active data from the default data, the remaining ones will be the inactive data specific to the CR.
Basically, by passing BP number and CR number into IT_SEL, active data will always be the one activated for the BP and appear in the parallel CRs, and for default data, it will return what is shown in the CR screen, which means active data for the BP and inactive data of current CR.
If anyone has the same requirement and different resolution, please feel free to drop a comment. Till then, we will leave this as our primitive solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
68 | |
9 | |
8 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.