Solved: Program BBP_EXTREQ_TRANS failure

ravindra_mantri2 · ‎11-19-2007

Hi All,

We are using ECS of SRM 5.0.

When we are executing BBP_EXTREQ_TRANS report to create shopping cart in SRM using PR generated in backend, it is getting stuck in SMQ1 (outbound queue in R/3) with status "ANORETRY". Once PR is created, EPRTRANS table is getting updated with relevant PR number.

Checked log into SLG1, but nothing found.

Following config is completed:-

1. RFC user (as Service) created in R/3 as well as SRM as well as has been maintained in Org structure and local Pur Org and P Grp is assigned to it.

2. In R/3, Tables V_160EX & PR are maintained.

3. replicated vendor, material master, plant , product categories from R/3 to SRM.

Please revert ASAP.

Points will be given for appropriate answers.

rgds,

Ravi

Former Member · ‎11-19-2007

Hi

<b>Please see related links -></b>

Do let me know.

Regards

- Atul

ravindra_mantri2 · ‎11-20-2007

Thanks all of you for info.

But still the problem continues...

I tried creating PR in R/3 with account assignment as cost center and system transferred it to SRM creating Shopping cart. but when i am trying for stock material PR, it is failing to transfer.

Checked SMQ1 in R/3 and still got the same error message saying " Ext requirements can be created, check the application log".

I don't know where to see the log as SLG1 does not show anything in R/3.

rgds,

Ravi

Former Member · ‎11-20-2007

Hi Ravi,

The "ANORETRY" status can come for many reasons. Check whether any of the following reasons exist in your case.

1. In case of the wrong RFC / ALE user assignment. You can verify this using SM59 transaction.The RFC user should have SAP_ALL access.

2. In case the Accounting view is not maintained for the material

3. In case of cost center P.R for a material (not free text)

Going by your info. it looks the settings made in R/3 are absolutely fine. In PDP (Plan driven procurement) scenario a channel needs to be created parallel to the company code and the RFC / ALE user needs to be assigned to this channel and not directly to the P.group.

The Org. i.d of the channel needs to be maintained in the Responsibility tab of P.Group under organizational responsibility column.

Also check all the attributes once again for the org. structure.

Hope this will help you in resolving the issues.Clarifications are welcome.

Award points for suitable answers.

Rgds,

Teja

Former Member · ‎11-19-2007

Hi Ravi,

1. As I noticed that you are using RFC user as service user, while as far as I understand, it should be system user.

2. What is the error detail when you double click the "ANORETYR", is that giving a better clue or not?

SG.

Former Member · ‎11-19-2007

Hi,

The program BBP_EXTREQ_TRANSFER is used to transfer the PReq from the backend to SRM. Table EPRTRANS have information about PReq to transfer.

Configuration guide on Plan-Driven Procurement(PDP) with Plant Maintanance available on http://service.sap.com/instguides (Business Suite\SRM)

Using transaction SMQ2, check the inbound queue in the Enterprise Buyer system and activate it if necessary

Integration of external requirements for Enterprice Buyer Professional

If purchase requisitions are to be procured via an external procurement system, these are transferred to the target system by means of report RPRSEL01. For this purpose, report RPRSEL01 reads table EPRTRANS which collects the requirements to be transferred. To do this, you must either start the report manually or schedule it periodically. The length of the period depends on the number of requirements to be transferred. A date is assigned to the report as an additional criterion. This date determines until which release date the purchase requisitions are to be transferred. If the release date lies after the date specified in the report, the purchase requisition is not transferred. The transfer itself is carried out via qRfc (Queued Remote Function Call, see also standard documentation). It is returned to the calling system if an error occurs in the target system for which there might not be a solution. In this case, the queue of the qRfc is blocked and all subsequent transfers cannot be carried out. The qRfc monitor (Transaction SMQ1) is used to check the queue. Check this monitor if the external requirements to be procured do not get to the target system. Furthermore, SAP recommends you to check this monitor from time to time.

If errors occur, you can generally solve these in two ways:

1. Delete the failed call in the qRfc monitor.

When doing so, note that there is a loss of information. In other words, the currently failed transfer of the purchase requisition is lost. If this is required, for example, for time reasons, you can restart the transfer in two ways.

Enter the purchase requisition manually in table EPRTRANS with status 2 or

Make a manual change to the affected items of the purchase requisition.

However, in both cases, analyze the error cause and solve it before the new transfer.

2. If possible, eliminate the error cause in the target system and restart the queue of the qRfc in question. Read also the standard documentation on the qRfc.

You can view error messages from the target system through forward navigation in the qRfc monitor.

Report RPRSEL01 uses "RPRSEL01" as a standard name for the qRfc queue. This name can be overwritten during the call of the report.

Prerequisites for External Requirements

http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/c0/5ee6415b006024e10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/55/4af54b688211d4977e0004ac962ee6/frameset.htm

See the foll threads for more pointers:

BR,

Disha.

<b>Pls reward points for useful answers.</b>