Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI

[Former Member]

Hi!

Somebody knows

How can be selected the scenario (Extended Classic or Classic) to process the SC, using BBP_EXTLOCALPO_BADI?

Tkx

[yann_bouillut · Accepted solution]

Hi Susana,

Classic or standalone scenario are by default activated.

All you have to do is to configure the system correctly (mainly through the organizational structure attributes and customizing point : SRM Server -> Technical Basic Settings -> Define Backend Systems for Product Category)

Once you have configured the classic scenario,the Extended classic scenario (ECS) can be activated through :

Path in the Implementation Guide (IMG): SRM Server -> Cross-Application Basic Settings -> Activate Extended Classic Scenario.

The badi "Control Extended Classic Scenario" can be used to code your own data that will determine conditions where ECS is to be used.

Kind regards,

Yann

[Former Member · Accepted solution]

HI Yann,

Do you mean that, using BBP_EXTLOCALPO_BADI I could code some conditions where ECS is to be used or not?

For example, for company code 1234 never use ECS. Inside thid BADI, could I mark some field(?) that indicate not to use the ECS when company code = 1234?

Thx,

Susana

[yann_bouillut · Accepted solution]

Hi Suzana,

Yes you can use your own conditions to control ECS activation.

Example is correct.

I do not understand your question "Inside thid BADI, could I mark some field(?) that indicate not to use the ECS when company code = 1234?" : could you clarify your question ?

Kind regards,

Yann

[Former Member · Accepted solution]

Hi Yann,

I try to explain it better.

I mean, in order to activate or not de ECS scenario for an specific condition. I could create an implementation of BBP_EXTLOCALPO_BADI.

Inside this BADI implementation I could code some condition in order to activate or not the ECS.

<b>But how must I proceed to activate the ECS?</b> Is there some field in the badi interface that I have to inform?

Thx,

Susana

[yann_bouillut · Accepted solution]

Hi Susana,

To just activate the ECS with standard conditions (product category criteria), you just have to activate (match icon) the badi.

Then if you xant to add your own condition criteria, you have to code it in the badi.

Kind regards,

Yann

[Former Member · Accepted solution]

Hi Susana,

You will have to implement and code BAdI as follows -

I am working on extended class scenario, In my case, if procurement card details are entered, I need to switch off extended classic. See example code below.

Please reward few points, if you find this answer helpful.

Regards.

Pras

method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.

IF item_data-pcard NE SPACE. " i.e. P-Card Entered.

MOVE ' ' TO bbp_extpo_gl-bbpexpo. "<Extended classic switched off.

ENDIF.

endmethod.

[Former Member · Accepted solution]

Hi Susana did u get the solution for this problem? If yes can u please let me know?

HI Pras, i could not able to find pcard field in DETERMINE_EXTPO method, can u please give me more details about this .. method and field name ..

u said item_data-pcard but in item data i didnt c any thing pcard.

Thanks

Murali

[Former Member · Accepted solution]

Hi Susana,

You are right: before talking about de-activating ECS or not in this BADI, this scenario must first be activated.

This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.

Here is the IMG path:

<i>

SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.</i>

You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.

Rgds

Christophe

PS: please reward points for helpfull answers

[Former Member · Accepted solution]

Hi Murali,

In the DETERMINE_EXTPO method is not the pcard field. To get the SC data, you must access it with a field symbol. Here is an example:

CONSTANTS: c_fieldname TYPE string VALUE '(SAPLBBP_SC_UI_ITS)GS_SC'.

• Field symbols

FIELD-SYMBOLS <f_sc> TYPE bbps_sc_app_document.

• Assigning SC data to <f_sc>

ASSIGN (c_fieldname) TO <f_sc>.

And so, you have the SC data in <f_sc>.

I hope this help you.

Regards,

Su

Message was edited by: Suzor .

[Former Member · Accepted solution]

Hi Su,

I've tried using your code below and it works perfectly with Shopping cart approval from the detailed screen. However when I try to approve from the overview screen Error: Field symbol has not yet been assigned.

Do you know of any field symbol that I may use for the SHC approval screen?

CONSTANTS: c_fieldname TYPE string VALUE '(SAPLBBP_SC_UI_ITS)GS_SC'.

• Field symbols

FIELD-SYMBOLS <f_sc> TYPE bbps_sc_app_document.

• Assigning SC data to <f_sc>

ASSIGN (c_fieldname) TO <f_sc>.

[Former Member]

Hi Susana,

To be more specific, you cannot use company code as a criteria to determine whether extended classic is turned on by the BADI or not. Company code and purch. org. are not available in the ITEM_DATA structure of the shopping cart BADI - bad design by SAP.

-Brian