PO not generated at backend in classic scenario

Hi,
I am working with SRM 5.0 in classic scenario.
1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
PO - From 3005000000 to 3008000000
2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
PO - From 3004000000 to 3009999999
4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
I see the following description in Admin login:
Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:
PO no. 3005000532 is picked from no. range PO defined in SRM.
But, in SC screen, I do not see any follow-on documents.
When I check BBP_PD, I find following data:
BE_OBJECT_TYPE    -> BUS2012         -> Follow on Document Object Type in backend system
BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
(However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
BE_INFO_REC    -> 5300002566
Also, I can see two lines highlighted in Red under Stats:
                       Status                            Description                 Inactive
HEADER          I1015                         Awaiting Approval                X
0000000001      I1111                    Item in Transfer Process           X
My doubt is that ,
a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
Why there is an error in transmission of PO?
Please help.
thanks

plz see Peter instructions in this thread
SC: Error in transmission BAPI 001
regards
Muthu

Similar Messages

POs are not available in Backend Ext Classic Scenario

Hi All,
Working with SRM 5 and Backend 4.6. in Extended Classic scenario.
For one plant the PO created in the SRM does not get replicated to the Backend whereas for other
Plants it happens.
Any body faced this before,pl give clues.
Thanks & Regards,
Nagarajan

Hi
(1)Is that PO in error in transfer?
(2)Hope you have defined local flag when your defined srm system.
(3) What about communication rfc users profile in both system.
(4) Hope RFC definition and logical system name are same/
BR
Muthu

Confirmation done in EBP but SES not generated in backend

Hello Team,
Below is the scenarion (SRM 4.0 Classic)
1. Number of confirmation have been done for Limit SC
2. Some confirmation successfully generated SES(Service Entry Sheets) in backend
3. While few confirmations have not successfully generated SES in backend.
Can anyone advise what is the issue and how it can be traced / resolved...
Thanks,
Dhananjay

Hello Nikhil,
Correct me if I am wrong.
In this case the confirmation in EBP is for Services, and hence in backend SES would get generated, and once this SES is approved/accepted, GR would get posted automatically.
Also, the confirmations, which are successful, I am not able to find any IDOCs.
I believe the SES is getting created via RFC.
Pls help me know, in this case can I make use of this FM BBP_PD_CONF_TRANSFER_V2?
Thanks,
DHananjay

Number of document created in th backend in the classic scenario?

Dear Experts,
Could you please tell me the number of document and its details created in the ECC backend in the below cases?
1. Case 1:
Define backend objects:Purchase requistion created if no stock available.
Is it correct that the system will create two documents here? The first document will be Purchase Requisition
( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
2. Case 2:
Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
Is it not a violation of standard classic scenario if only one document is created?
Thanks and regards,
Ranjan

Hi,
In other words in the shopping cart is approved
1) If the source is assigned -It will create a P.O in the backend (Classic)
2) If the source is NOT assigned -It will create a P.R in the backend (Classic) .. you have to assign a source
Regards
G.Ganesh Kumar

Classic Scenario -Backend settings

Hi,
In the classic scenario the following is done in SRM
1. In the PPOMA_BBP - we are defining the Attribute : BSA - as EC
2. How this is linking with the Backend in SAP R/3.
We have created the Logical system-in SM59 and RFC are assigned to SRM and SAP R/3.
Backend SAP R/3
1. Number Ranges for P.O defined?
In SAP R/3 -SPRO -Define Document types -We can see the Type EC
How is the linking is achieved in SRM and Backend in classic scenario,.
Can you explain in details what are the setting done in SRM and SAP R/3 to achieve the Classic scenario
Regards
G.Ganesh Kumar

Hi,
Some of the basic settings around document types in SRM for the classic scenario which you have to define are the following :
In R/3 system:
1. define number range for the POs , PREQs and Reservations which will be created in R/3 system,
2. create document types for PO, PREQs and Reservations and assign to them the number of the number ranges created in step 1 - this is the doc type which you have to assign to BSA attribute
In SRM system:
1. define SRM transaction types
2. Define shopping cart number range, as well as the number range of the follow on documents created in R/3 system
3. Define number range for local confirmations of services and goods receipts
Regards,
Desislava

How differentiate POs classic scenario and POs extended classic scenario?

Hi Gurus,
Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
The objective is determining the following: Is necessary differentiating POs created in SRM of importation and should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
Thanks for your help!!

Hello,
Yes this is possible.
You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
Then you set exceptions in the BAdI.
Regards
Franck

PO is not generated for completed SC in SRM.70 classic scenario.

Hi,
I am working on SRM 7.0 - Classic scenario.
When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process. even we are adding items from catalog.
If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
This is the case even for the SC ordered using catalog materials.
I have checked following configuration and it seems to be ok.
1. 'Define objects in backend system's
2. Number ranges definition in SRM and ECC
3. Document type attribute -BSA in PPOMA_BBP
Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
RZ20 does not show any error for the SC with status I1111.
Is there any sepcial FM to push the SC in SRM 7.0?
Any help/tips would be highly appreciated. Thanks in advance.
Thanks,
Ravi

learnt that PO number has generated in SRM and the same PO number not exist in ECC.
check SM58 , rz20 log or Application monitor for the shopping cart.
or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
let us see .
1. what is the settings in define backend OBJECTS
2. check all basic data in the shopping cart - especially org data
3. run bbp_check_consistancy report for your id?
4. every user has the same issue?
SEE THE RICHARDO technique
http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
Muthu
Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
1480994 How to process a shopping cart with status I1111
Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Classic scenario-SC not transferred to backend,short dump in ecc

hi Guru's,
Classic scenario, sc not transferred to backend, executed FM bbp_pd_sc_resubmit, short dump occurred in the backend stating call function not found
please help
short dump file attached
regards,
kiran

Hi Kiran,
Could you please send the DUMP for analysis.
Please try to use this -
This is the new report BBP_SC_AUTO_RETRANSFER to change the status from
I1111 Item in Transfer Process
I1112 Error in transfer/ transmission
Thanks,
From RBEI,
Snehal

Urgent ! Purchase Requisition not created in Backend Classic Scenario

Hello All,
I am implementing the classic scenario SRM 5.5. We have replicated the material form the backend to SRM system. Also we have made the necessary config such as maintain backend system, Define Backend System for Product Category, Define Number Ranges for Shopping Carts and Follow-on Document, Define Number Ranges per Backend System for Follow-on Document. Now the problem i am facing is that in the dev system SC with line item with desc and the product (material replicated from backend) as line items are created and their PR is created in the backend. However the same is not happening in the QA system. Only those SC with line item as Desc/text only are created in the backend and those having have product id dont transfer to create PR in the backend. There is no message in the RZ20, SM13, ST22, SM21 etc. Alsowhen i try to tranfer it using the FM BBP_PD_SC_TRANSFER it is created successfully and there is entry in BBP_DOCUMENT_TAB which is cleared afetr clean_reqreq_up is run. I am not sure whats is going wrong. Please help me out guys.
Thanks
Karthik

Hi Andy,
Thanks for the quick responses. I dont see any PR doc no and neither the BUS object type in BBP_PD item details. Please see the o/p below
BE_LOG_SYSTEM                R3QAS400
BE_OBJ_ITEM
BE_OBJECT_TYPE
BE_OBJECT_ID
BE_REFOBJ_TYPE
BE_REFOBJ
BE_REFOBJ_ITEM
BE_REFOBJ_SBITM
BE_REFOBJ_TYPE2
BE_REFOBJ2
BE_REFOBJ_ITEM2
BE_REFOBJ_FYEAR2             0000
BE_STGE_LOC
BE_PLANT                     IE01
BE_BATCH
BE_VAL_TYPE
BE_MOVE_REAS                 0000
BE_EXPERYDATE                000000
BE_PUR_GROUP                 440
BE_PUR_ORG                   IE01
BE_CO_CODE                   IE01
BE_DOC_TYPE                  EC
BE_ACCREQUIRED
BE_SP_STK_IND
BE_INFO_REC
BE_MOVE_TYPE                 101, so i am not sure what could be going wrong.
Is there any way i can debug it and find out what the cause is,
though the calls to the bapis are asynchronous. Also just for the reference sake my backend is 46C. I have been grazing through the notes but haven't found a substantial one.

IDOCs not generating with classic scenario

Hi,
We are with SRM 7 with Classic Scenario.
Issue : SRM Org. structure is replicated from ECC system through IDOCS. But, suddently, no IDOCs are getting generated in SRM after we run PFAL in ECC.
IDOC is getting created in ECC after we run PFAL but not creating in SRM.
Your inputs are appreciated.
Thanks
Nag

Hi,
We have faced same issue.
You first check with tcode WE05 in both SRM & ECC. You will get to know which idocs present (transferred).
You can process unexecuted idocs using tcode BD87.
After processing idocs you must run distribution model.
This way we resolved our issue.
Regards,

POR transferred into MM(Backend) system in Extended Classic Scenario

I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9
As we are successfully send PO from EBP to SUS.
Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
Please tell us, Provided Solution will be really appreaciated.
Thanks.
Regards,
Pawan Keshwani

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
<b>Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end</b>
BR,
Disha.
Pls reward points for useful answers.

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

SRM 7.0: Classic Scenario no PO is created only PR is generated

Hi Gurus,
I am working on SRM 7.0 - Classic scenario.
When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process.
If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains I1111 i.e. item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
This is the case even for the SC ordered using catalog materials.
I have checked following configuration and it seems to be ok.
1. 'Define objects in backend system's
2. Number ranges definition in SRM and ECC
3. Document type attribute -BSA in PPOMA_BBP
Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
RZ20 does not show any error for the SC with status I1111.
Is there any sepcial FM to push the SC in SRM 7.0?
Any help/tips would be highly appreciated. Thanks in advance.
Best Regards,
Amit

Hi Amit
what is the setting here
1. 'Define objects in backend system's
is it a prefered vendor or fixed vendor
update the partner function in bbp_pd here
if it is 39 - you wil recive pr
it is 19 you will get PO
i am afraid , you stated that catalog sc stoo this problem but during debugging check what is the partne rfunction...
there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
MOREOVER NOTE SAYS POSSIBLE REASONS ..
Note 336658 - Purch req instead of purch order created in backend
BR
Muthu

Freight is not updated in R/3 in the Extended Classic scenario

Friends,
Freight is not updated in R/3 in the Extended Classic scenario.
Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
We have created a condition for Freight (Value and Percentage)in Create
Payment Conditions using the following menu path:
spro
--> Supplier Relationship Management
--> SRM Server
--> Cross-Application Basic Settings
--> Pricing
--> Process Payment Conditions
When creating a Purchase Order in SRM in the "Item Data" tab, there is
a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
from the drop down menu. Here Freight is available. Add Freight and
the PO record in SRM is updated with the Freight Condition. However,
upon ordering, the Freight condition does not transfer to the PO
recordin R/3.
We've heard this can be achieved by enhancement: only ie by implementing
set of BADIs.. But does anyone know WHICH BADIs we need? Or how we could find out? Thanks.

Hi
<b> You can either of these BADIs to handlwe the scenario.</b>
BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system
BBP_ECS_PO_OUT_BADI ECS: PO Transfer to Logistics Backend
BBP_EXTLOCALPO_BADI Control Extended Classic Scenario
Hope this will help.
Please reward suitable points.
Regards
- Atul

PO not generated at backend in classic scenario

Similar Messages

Maybe you are looking for