Item in Transfer process

[Former Member]

Hi,

One SC is in "item in transfer process" for more than 10 days...

is there any FM to release those from "item in Transfer ", if then then do let me know

Sameer

[peter_novoth · Accepted solution]

Hi Sameer,

The official way:

Do you have entries in the alert monitor for this SC? If yes, you can process it.

If not, execute the report BBP_ALERT_SB_NOTTRANSFERED as in the note 441768 described.This will create entries in the alert monitor for the SC, which can be proceed (deleted or retransfered) by the administrator via the Browser.

Practical way (for test system):

Execute the BBP_PD_SC_TRANSFER with the header GUID of the SC.

Regards,

Peter

[Former Member · Accepted solution]

Hi Sameer,

Are you able to resolve your issue?

In addition to suggestions given above, you can recreate the event <SWUE> and select the evet RESUBMITPOSITION.

Regards,

Gopesh

[Former Member]

Thanks Peter

[Former Member]

Experts,

I have tried all the ways... but still it is in "item in transfer"

rg

sam

[peter_novoth]

Hi Sam,

in this case I suppose there is a problem with the document itself, and therefore can not be transfered to the backend system, or can not be created there.

The problem has to be debugged. Set a breakpoint at the place where we send the SC data into the backend system. Depending on the follow-on document type (PR/PO and backend system release) go into the transaction SE24, and set a breakpoint in the method CREATE_DOCUMENT of the following modules:

- In case the follow-on document supposed to be a PO:

BE release Class

R/3_4.6C -> CL_BBP_BS_ADAPTER_PO_CRT_46C

R/3_4.70 -> CL_BBP_BS_ADAPTER_PO_CRT_470_1

ERP_1.0 -> CL_BBP_BS_ADAPTER_PO_CRT_ERP10

ERP_2.0 -> CL_BBP_BS_ADAPTER_PO_CRT_ERP10

- In case the follow-on document supposed to be a PR:

BE release Class

ERP_1.0 -> CL_BBP_BS_ADAPTER_RQ_CRT_470

ERP_2.0 -> CL_BBP_BS_ADAPTER_RQ_CRT_470

R/3_4.6C -> CL_BBP_BS_ADAPTER_RQ_CRT_46C

R/3_4.70 -> CL_BBP_BS_ADAPTER_RQ_CRT_470

Then start the SPOOLER:

- In case the follow-on document supposed to be a PO start the SE37 -> SPOOL_PO_CREATE, where:

-- REQNO = SC number

-- PO_NUMBER = PO number (from the BBP_PD -> Item detail -> BBP_PDBEI-BE_OBJECT_ID)

-- IV_BE_LOGSYS -> leave it empty

- In case the follow-on document supposed to be a PR start the SE37 -> SPOOL_RQ_CREATE, where:

-- REQNO = SC number

-- REQUIS_NUMBER = RQ number (from the BBP_PD -> Item detail -> BBP_PDBEI-BE_OBJECT_ID)

-- IV_BE_LOGSYS -> leave it empty

When you execute the spooler with F8, you will have a breakpoint at the place, where the SRM calls the backend. E.g. at the place

 CALL FUNCTION 'BAPI_REQUISITION_CREATE' 

If you skip now the backend call with F6, you will see in the return table (in case of RQ in the as_rq_out-return) what's wrong in the backend.

Other option, that you fill the test data with FBGENDAT (see the note 539978), restart the spooler, and then you can test the result directly in the backend system (BAPI_PO_CREATE1 or BAPI_REQUISITION_CREATE).

Regards,

Peter

[Former Member]

Hi,

You can transfer using function module BBP_PD_SC_TRANSFER.

Let me know if you want more information.

Regards

Sreedhar Vetcha

[former_member183819]

Hi

Please see the related links discussed the same issue.

regards

Muthu