RFC Call from SRM to ECC schedule job immediately for BBP_EXTREQ_TRANSFER

[Former Member]

Hi SRM Experts,

I have an custom application(SRM) where i need to schedule back ground job (start immediately)from that application for the report BBP_EXTREQ_TRANSFER(ECC) and after the job done....i will retrive the

PR transfered details for further processing.Can any one help finding the right function module to call from SRM.

Full points will be awarded

Thanks,

Radha

[Former Member]

Hi

As muthu Said, The BBP_EXTRAQ_TRANSFER is a schedule job which takes all the back end PR to SRM, as a Shopping Carts. This job run at over night.Once in a day.

But BBP_REQREQ_TRANSFER is for strucked SC's. i.e if any SC approved but the follow-on doucments are not created for those sc we need to run this.

Regards

Satish

[former_member183819]

Hi Radha

took from old link...from Atul replies .....

Function Module - BBP_EXTREQ_TRANSFER calls BBP_BC_EXTREQ_INB on SRM side. This function module calls BAPI_SCEC_CREATE.

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.

Related links ->

Note 1027506 BBP_EXTREQ_TRANSFER: ANORETRY for PR with different vendors

Check if external profile is flagged (EBAN-EPROFILE = X) for those PRs which are in EPRTRANS.

Also check if RFC connection is OK between R3 and SRM and RFC user is same as maintained in Entry channel in SRM. RFC user should be service user.

So that temporary problems (for example an external request which is locked in the SRM server) do not have the effect that the qRFC comes to a permanent standstill, you can make sure that the transfer of the purchase requisition is started by the system again. For detailed information on this, see the SAP help for the qRFC in the 'Administration of the outbound queue'. This is only a summary:

Use Transaction SMQS to register the RFC destination which is used for the outbound queue.

Use Transaction SM36 to schedule program RSQOWKEX. This program makes sure that possibly hanging queues are triggered again.

In addition, you have the option to monitor qRFC using the Alert Monitor. For more information on this, see the SAP help for the Alert Monitor under 'Special monitoring functions of the Alert Monitor -> Monitoring qRFC and tRFC calls'.

See SAP OSS Notes ->

Note 650333 - Hanging qRFC after transfer of Preqs to SRM

- please see some fishbone analysis on PDP process from Yann and Marchin.

[former_member183819]

Hi Radha

Did you check this FM bbp_reqreq_transfer in EBP ? Actually this one is creating follow on document for external request. you can search EBP FM in the BB_EXTREQ_transfer program itself.

even the top FM just pushes the EPRTRANS table to srm.

regards

Muthu