cancel
Showing results for 
Search instead for 
Did you mean: 

SRM Function called by BBP_EXTREQ_TRANSFER

yann_bouillut
Active Contributor
0 Kudos

Hi,

I pretty well understood the PDP process.

However, i would like to know which SRM function is called by program bbp_extreq_transfer to create the requirement in the sourcing cockpit ?

Kind regards,

Yann

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Yann,

FM BBP_EXTREQ_TRANSFER calls BBP_BC_EXTREQ_INB on SRM side.

This function module calls BAPI_SCEC_CREATE.

Kind Regards,

Marcin Gajewski

yann_bouillut
Active Contributor
0 Kudos

Hi Marcin,

Thanks !

Do you know why the BAPI_SCEC_CREATE is not called directly ?

Kind regards,

Yann

Former Member
0 Kudos

Hi,

Program BBP_EXTREQ_TRANSFER on backend side do the following:

- load a local stored copy of transfer table EPRTRANS

- create a package from the transfer table without breaks with one PR

- enqueue the corresponding EBAN entries

- transfer the package <-- in this perform we have BBP_BC_EXTREQ_INB and BAPI_SCEC_CREATE function module.

- dequeue the package

Before call BAPI_SCEC_CREATE, program checks if the incoming requirement is arleady existing, derermine limit positions, fill partner table in "i_bup" structure, check category if we don't have product id, pricing for IPC etc.

This information are on SRM side, maybe that's why backend system don't call BAPI_SCEC_CREATE function module directly.

Regards,

Marcin

yann_bouillut
Active Contributor
0 Kudos

Hi Marcin,

Thanks for the additional elements

Do you know where (which function, where in the code) SRM is selecting the SC type for sourcing cockpit instead of the standard SC ?

My requirement is to adapt the standard PDP to create a standard SC instead of a requirement in the sourcing cockpit.

Kind regards,

Yann

yann_bouillut
Active Contributor
0 Kudos

Hi,

I noticed :

SC header level -> subtype = ER (External Requirement)

SC item level -> SOURCE_REL_IND = X (valid for sourcing cockpit)

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann,

Yes, subtype ER and flag SOURCE_REL_IND thats one.

I think, SRM decide where to put SC, because requirements are put to EPRTRANS queue w/o preffered vendor and prices. In SRM we decide where to put SC's in SPRO -> SRM Server -> Sourcing -> Define Interactive Sourcing for product categories.

I look in system to find other solutions.

Regards,

Marcin

Former Member
0 Kudos

Hi,

You just need to remove the config for SOURCING in SRM ,so that you can create SC in the Std way through SHOP trascn and not through sourcing.

BR,

Disha.

yann_bouillut
Active Contributor
0 Kudos

Hi Disha,

I don't think taht standard configuration for sourcing in SRM has anything to do with this. I do believe that the program is flagging the sourcing box automatically, whatever you put in the SRm configuration.

Am i wrong ?

Kind regards,

Yann

Former Member
0 Kudos

Hi Yann,

While debugging BBP_EXTREQ_TRANSFER I found following code in BAPI_SCEC_CREATE.

 
* Try to source the items                
   IF i_header-auto_source = c_on.        
     CALL FUNCTION 'BBP_EXTREQ_SOURCING'  
       TABLES                             
         it_org   = lt_i_orgdata          
         ct_items = lt_i_items            
         ct_bup   = lt_i_partner.         
   ENDIF.                                 

Marcin

yann_bouillut
Active Contributor
0 Kudos

Hi Marcin,

Thanks for the additional info.

Kind regards,

Yann