Skip to Content

C1 Screening Built-in Functionality

May 11, 2017 at 08:54 AM


avatar image

Hello - I know that C1 screening works and only considers BPs that are released and ignores those that are blocked. Now I would like to know if this is a built in functionality of C1 screening in GTS? Is there a way to modify it to also screen even those BPs that are already in blockes status?


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Mouaz BEN REDJEB May 12, 2017 at 01:46 PM

Hi Luke,

I had a look at this issue and it is actually hard coded by SAP, see program /SAPSLL/LSPL_CHECK_SCEN_SELF02, form "scen_sel_bp_c".

That being said, there is may be a workaround:

1. Load SPL file with updates

2. Run C1 screening (where only released BP are considered and the blocked BPs are excluded)

3. Run B1 screening and tick the option to select only the blocked partners. Hence the BPs excluded from the C1 screening will be taken into account in this B1 screening. The downside of this is the BPs are checked against all SPL (old and new data), not just the new data in the SPL update file....



Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Mouaz,

Thanks for answering, So you mean we need to execute step 3 instead?

Because the C1 screening while running already has issue with consuming all the threads in memory.

So executing B1 after C1 screening wil not make sense.

I think you mean only B1 with only blocked BP's?




Hi Kaushik,

I believe that the standard behaviour of the C1 screening is meant for that: why re-screen a BP if it is already blocked by a previous screening? Why consume memory and CPU power if the BP is already blocked?

So the answer I gave to Luke was a kind of workaround to the standard behaviour (already blocked BPs are excluded from C1 screening)... but as I have said, running B1 check will check all SPL data (new and old) and of course this will have some effects on the performances... it is really just a workaround, to be used wisely and in case there is a real benefit for that...

If you run B1 only for blocked BPs, then you will never catch BPs that are released but should be blocked with updated SPL data...

In a nutshell:

- Released BP excluded from C1 screening make sense (why re-screen an already blocked BP? why use CPU and memory for an already blocked BP?)

- If you have a good reason, you can run B1 screening selecting only the blocked BPs in order to check them for old and new SPL data, in order to overcome the limitation of C1 screening