Create po in backend

hi
I am on SRM 7.01 and using the classic scenario
process
SC created in SRM - > SC goes to approving ->Manager approved the Sc -> system create PR or PO or RS Automatically in backend as a follow on doc
problem:
when purchaser create sc and manager approve it no follow on doc created until i run FM :BBP_PD_SC_TRANSFER
and when i run this FM PR and RS are created in backend but no PO are created
i have 2 question
1. why i need run BBP_PD_SC_TRANSFER to created follow on document?
2.why i cant created any PO?

this is the status of SC befor runnig the FM :
Stats:
           Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1106          Shopping cart ordered
HEADER     I1129          Approved
and this i the workflow status:
orkflow Item:
orkitem-ID        000000006312
ask               WS40000014
ext               SRM Approval Process for Document ID 10000444 (GUID: 005056AF0A3B1ED487A9ED72D935F7B1)
tatus             COMPLETED
tatustext
ate               06.08.2014
ime               13:27:25
ant this is status of SC after implmntion the FM : BBP_PD_SC_TRANSFER
Stats:
           Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1106          Shopping cart ordered
HEADER     I1129          Approved
0000000001 I1111          Item in Transfer Process       X
0000000001 I1112          Error in transmission

Similar Messages

Create PO at backend from SRM

Hi
I have below scenario to create PO at backend from SRM
1)SRM Shopping cart(assign contract number) ->Create PO at ERP
2)SRM Shopping cart ->RFx-> RFx Response -> Create PO at ERP.
Can you pls confirm below doubts.
1) Does the BAPI(BAPI_PO_CREATE1) is called for both above scenario?
2) Also I want to know how the attachment transfer is carried out from SRM to Backend.
I found note to implement BADI BBP_CREATE_BE_PO_NEW at SRM for backend transfer.
I implemented as follows including setting at ERP DC10,DC20,DC30.
method IF_EX_BBP_CREATE_BE_PO_NEW~FILL_PO_INTERFACE1.
Enable transfer of attachments in classic scenario
cs_ctrl_att-BE_DOC_TYPE = 'SRM'.
cs_ctrl_att-BE_STORAGE_CAT = 'ZDMS_CT_CT'.
cs_ctrl_att-TRANSFER_ACTIVE = 'X'.
endmethod.
But i could not understand the general flow how the file attachment at SRM Portal is transferred to ERP DMS.
can you please explain.
Regards
Chandra

Hi Masa
Thanks for your reply.
yes, we are working on SRM7.0 EHP4.0.
As you said, I can see in PI SXMB_MONI messages the PO is created in ERP backend.
But why its going thru ESOA? Why its not taking above BAPIs and RFC to transfer the PO datas?
Also again the attachment is missing in PO created. its not transferred in ESOA standard?
Addon possible to solve the problem?
For your information.
We transferred ERP PR file attachment as URL from ERP to SRM using BBP_TRANSFER program.
Now after attaching file in SRM portal at RFX ,how PO is transffered to ERP?
Pls guide me what should be done?
Regards
handra

EBP 3.0. Restrict Create PO in backend

Dear SRM gurus,
We use EBP 3.0, backend R/3 (4.7 enterprise). We have configuration inplace where a PO is created in the backend, per requirements. However, for one particular vendor, we need to have a minimum price limit set for automatic PO creation, due to additional charges. One option we were thinking is to send it as a PR instead of PO and may be use an user exit for ME59 and combine PR's to generate a combined PO. We also would like to have a check on ME59 to make sure that the minimum prrice is established. Would it be better to do this using condition types in the R/3 or would you suggest any other ways. As for transfering it to R/3 as a PR instead of PO, would it be appropriate to use BADi BBP_TARGET_OBJECTS. If so, would one of you be kind enough to help me with the code. I am not an ABAPer and do not have one available for some time. Any assistance would be greatly appreciated for both on EBP side and on R/3.
Kind Regards,
Reddy

Hi KS,
You can use badi to convert prefered to fixed vendor in your shopping cart.
Thus, you will be able to create a PO in R/3 instead of a purchase requisition.
Please see my answer here :
Re: convert prefered vendor to vendor
Kind regards,
Yann

PO is created in the Backend Instead of PR - Classic Secnario - SRM 5.0

SRM experts,
My client has upgraded to SRM 5.0 and ECC 6.0 from SRM 3.0 and 4.6c version respectively. SRM is using classic scenario, so Shopping cart is created in SRM and Purchase Requisition and Purchase Orders are created in the backend system. In the Sources of supply tab, we will see the Vendor, Outline agreement and other information based on the Plant, Product category and Purchasing group we select in the shopping cart. If user selects the vendor with outline agreement in the sources of supply tab then Shopping cart will create Purchase order instead of Purchase requisition in the backend system. I am new at this clients site and client does not have any documentation about how these has been configure in the system. Can someone please help me to find out where the settings might have been made in the system to create Purchase order instead of Purchase requisition if shopping cart contains vendor with outline agreement. I am asking this question because we have another enhancement request with similar requirement but with different condition.
I will reward the points for helpful answers.
Thank you experts.
MP

Hi,
Could you checkthe foll cust link in SPRO:
Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders).
PO is created if you set the "*" for EITHER the purchasing group OR the product category.
SRM is creating PR or PO depending on:
- SRM customizing (ex: always external proc + PR if incomplete, PO if complete)
- the interpretation of SC data by R/3.
IF your SC is considered complete by SRM (but with a fixed vendor and not a preferred vendor) the system will check if it can create a PO in R/3.
For this, each item will request a META_INTERPRETE_DATA to R/3, asking if it can create a PO. If R/3 considers this data as incomplete, it will reply to create a PR.
Usual cases of R/3 PR creation instead of PO:
- prefered vendor in SRM (and not a fixed one)
- custom checks in user exits in R/3
- error messages in R/3 (ex: O6 334 In the case of a fixed vendor, please enter info record)
To debug without debuging into R/3, you can also try the following:
- use BADI DETERMINE_TARGET_OBJECT and force PO creation
- so the system will always try to create a PO
- R/3 won't create the PO (for the same reason as in META_INTERPRETE_DATA), and will raise an error in SRM
- finally you get the real error in application monitor (SC --> backend application errors
Related thread:
Re: PO not create from SC with source of supply in classic sena
BR,
Disha.
Pls reward points for useful answers.

PO not created in the backend for SC

Hi,
I am using SRM 5.0 and i created a shopping cart.. The shopping cart is ordered sccessflly but a PO is not created in the backend system.
I have made the follwing setting.
The backend system definition seems fine.
I have also defined the prodct category and the target system.
Number ranges are assigned in the SRM system.
I checked rz20 and did not find any errors there..
Shold i created a docment type EC in the backend MM system??
What else could i be missing. Please advise.

Hi,
You could check the return of FM B31I_INTERPRETE_DATA, which is called when a follow-on document is created in backend system.
Try to debug the shopping cart transfer, as specified in note 1173815. Perhaps the backend return message can be helpful.
Kind regards,
Ricardo

Is there any API or standard process to create structure from backend

Hi,
Is there any standard process to create structure from backend.I want to create 300 options for a option feature from backend.
Please let me know the API through which it can be done.
Best Regards,
AJ

AJ --
Configurator provides a "Custom Import" capability to automatically create structure. It is documented in Chapter 5 ("Populating the CZ Schema") of the Oracle Configurator Implementation Guide.
However, setting up a custom import may actually take you more time than just creating the Options manually in Configurator Developer. If the Options need to be duplicated across several Models, it may be advantageous to build them as Items in the Configurator Developer Item Master instead, and then use Populators to automatically create corresponding Options within your Option Feature(s).
Eogan

Shopping Cart - PO created in the backend

Hi,
Many SC have been approved but no PO was created in the backend ECC due to various reason, I want to know all the SC which was approved and whose PO was not created in the backend, Is there any way to find it???
regards,
Prabhu

Hi Prabhu,
Which version of SRM system you are in ? and waht scenario you have implemented i.e classic or extended classic scenario ?
There are OSS Notes available which have correction report in them which can gives you list of errreneous shopping cart that could help.
please refer to below OSS Note to see if that help.
729967
728536
if none of that help the logic would be to get all item guid from CRM_JEST which has status as I1111 active for those item GUID you can get the header guid from CRMD_ORDERADM_I and the from header guid you can get the SC number from CRMD_ORDERADM_H.
Hope this helps.
Cheers
Iftekhar Alam

How may spool request can I create in the backend?...

Hi Experts,
How may spool request can I create in the backend? If yes, is there anywhere in the system can I set this value to increase number of spool request per user.
Is there any condition which can prevent me create a new spool request?
Yes all of the answer above is answered, so is there any offfical document from SAP states them.
Thanks!
- Anthony-

Thx for the feedback. But, in fact, what was the real issue, originally?
I forgot to inform you of that:
1) [Note 193638 - Calculating spool number from file names as of 4.0A|http://service.sap.com/sap/support/notes/193638] (indicates the algorithm of UNIX file names). This note also indicates "For Release 4.0A, the maximum spool number has been increased from 99000 to 2000000000. The maximum number of output requests per spool request has been increased to 32767 as well."
2) I think I forgot one of your initial questions:
> Is there any condition which can prevent me create a new spool request?
By default, SAP tries to append pages to existing spools with same characteristics. If they are always different, a new spool request is always created. So, you may change some characteristics so that they are identical and SAP will reuse existing spools. See rules in [Note 85318 appending documents to existing spool requests|http://service.sap.com/sap/support/notes/85318].

GR cancel posted in SUS created 101 in backend

We are in SRM6.0 SP03.
We have implemented SRM-SUS (extended classic scenario). When we cancel GR in SUS it creates reversal in SRM but it created 101 in backend. The IDOC is having 101. Please help.
Thanks, Sachin

Virender,
thank you for your reply, what sounds strange to me that in my POWL for GRN I have the button CANCEL/DELETE and the system ask me if i really want to delete the selected GR just before giving back that strange message.... It looks like if the functionality exists but doesn't work.
Are you sure you can't cancel a GR in SRM, what should be the procedure in this case?
Thank you in advance,
Fuffo

Create Webservies from Backend

Hi
Any idea about how to create Webservices from Backend RFC/BAPI .

Hi,
Did you check the Web Services section of SDN ?
In the Developer Area, you will find an entry Web Services. Just expand : SAP NetWeaver -> Application Server -> Web Services
I will recommend the document titled "<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn?rid=/library/uuid/dab85be0-0601-0010-c6aa-b20626aa3cd5">a Code Free, Wizard-Driven Approach to Securing Web Services</a>".
Hope it helps.
Best regards,
Guillaume
Message was edited by: Guillaume Garcia
Added link to the document

SRM PR,PO is not getting created in ECC backend

HI
i create SC in classic scenario. and after the manager approve the SC the follow on Doc didnt create in ECC
i define object for po pr and reserve in backend
when i check FM :BBP_PD_SC_CHECK i havent any error message
but when i have chek the SC in RZ20 i have this error: Local Error: Shopping cart 0010000308: Error creating the follow-on document
and when i chek BBP_PD i have this status:
Stats:
           Status         Description                    Inactiv
HEADER     I1015          Awaiting Approval              X
HEADER     I1021          Created
HEADER     I1038          Complete
HEADER     I1106          Shopping cart ordered
HEADER     I1129          Approved
how to resolve this issue?
Regards
Elham

Dear Elham,
To find the solution of the problem I think you need to debug.
Follow below steps if this help you
a) Run the report "FBGENDAT"
b) Input the data as below screen shot
c) Then go to se37 execute FM : BAPI_PO_CREATE1
d) You will find the test data directory and test data will be saved as below
e) In this test date change PO number you should get the error which you are getting above.
Thanks
Ankit Jain

PO not getting created in the backend

Hi
I have made settings for R/3 PO to be created once a SC is approved, but I get the following errors in the "Application monitors>Shopping cart> backend application errors"
000Creation of PO using Enjoy BAPIunsuccessful
MEPO 085Check item number 0 in tabl
06 010Document contains no items
MEPO 071Item 00010 does not exist
Note: PR and reservations in R/3 are getting created as follow on docs for SC but onky PO creation is throwing these errors. PO is getting created if i manually try and create it in R/3, so i suppose theres nothing wrong with the data as well.
Regards,
Amol

Hi Sailatha,
I am new to this so can u pls tell me, how to check and rectify it step by step. Which are the transactions used and how to do the assignment.
Also what are the default message types to me maintained in the ALE customization. Currently i have the following messages maintained:
ACC_GOODS_MOVEMENT
ACLPAY
BBPCO
BBPIV
MBGMCR
Thanks & Regards,
Amol

SRM PR is not getting created in ECC backend

Hello Experts,
We are running SRM 7.0 with SRM-MDM Catalog, we are using SRM for shopping. We do have PI 7.11 running in the Environment as well.
We are on ECC 6.0 with Ehp 4.0
Purchase Order:
However we can see the PO creating successfully using PI.
Question, in the SRM table (BBP_FUNCTION_MAP), we see the object type: BUS2012 for ERP 4.0 has adapter name: /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP for when creating PO. Please see teh screen shot.
is this the reason that we need PI?
Purchase Requisition:
PR Creation is not working:
PR is not getting created in the ERP, PR uses Object type: BUS2105, Adpater CL_BBP_BS_ADAPTER_RQ_CRT_470 for ERP 4.0 System type, can you please tell me if the adapter is correct for ERP 4.0 system type?
I also have a question to ask:
1) Where did you see that PR/PO was send to PI System (PI1)? My understanding is that since ERP amd SRM are 2 ABAP Systems, why we cannot send the PR/PO directly to ERP system from SRM? Why do we need a middleware(PI) in between for this process? We should be able to USE BAPI function to do it correct?
Please advice.
Thanks
Kumar

yes, i could see a PR number with all this additional details as below.
Table   BBP_PDBEI
CLIENT                       453                                                              Client
GUID                         4CAEFA58EB9D005CE1008000AC1C2031                                 Globally Unique identifier
BE_LOG_SYSTEM                QA1400                                                           Logical System of Logistics Backend
BE_OBJ_ITEM                                                                                Follow-On Object Item in Back-End System
BE_OBJECT_TYPE               BUS2105                                                          Follow-On Document Object Type in Back-End System
BE_OBJECT_ID                 2000000167                                                       Follow-On Document Object ID in Back-End System
BE_REFOBJ_TYPE                                                                                Reference Object Type in Back-End System
BE_REFOBJ                                                                                Reference Object in Back-End System
BE_REFOBJ_ITEM                                                                                Reference Object Item in Back-End System
BE_REFOBJ_SBITM                                                                               Reference Object Sub-Position in Backend System
BE_REFOBJ_TYPE2                                                                               Reference Object Type in Back-End System
BE_REFOBJ2                                                                                Reference Object in Back-End System
BE_REFOBJ_ITEM2                                                                               Reference Object Item in Back-End System
BE_REFOBJ_FYEAR2             0000                                                             Reference Document Object - Fiscal Year in Back-End System
BE_STGE_LOC                                                                                Storage location
BE_PLANT                     2016                                                             Plant
BE_BATCH                                                                                Batch Number
BE_VAL_TYPE                                                                                Valuation type
BE_MOVE_REAS                 0000                                                             Reason for Movement
BE_EXPERYDATE                00000000                                                         Shelf Life Expiration Date
BE_PUR_GROUP                 206                                                              Purchasing group
BE_PUR_ORG                   2000                                                             Purchasing organization
BE_CO_CODE                   2000                                                             Company Code
BE_DOC_TYPE                  CLRQ                                                             Purchase Requisition Document Type
BE_ACCREQUIRED                                                                                Account Assignment for Logical Backend Required
BE_SP_STK_IND                                                                                Key for Special Stock Section
BE_INFO_REC                                                                                Number of purchasing info record
BE_MOVE_TYPE                 201                                                              Movement type (inventory management)
BE_PACKNO                    0000000000                                                       Package number
BE_INTROW                    0000000000                                                       Internal line number for limits
BE_ITEM_TEXT                                                                                Short Text of a Service Purchase Order Item
BE_PO_PRICE                  1                                                                Price from Backend
BE_UNLOAD_PT                 200                                                              Unloading Point in Backend
BE_DEL_IND                                                                                Deletion Indicator in Backend Documents
BE_TRACKING_NO                                                                                Requirement Tracking Number
BE_COND_TYPE                                                                                Condition Key
BE_COND_STEP                 000                                                              Level Number
BE_COND_COUNTER              00                                                               Condition counter

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

Create application using backend code

how to create application in excel using java backend code

This is a forum for sql server. Please post your question to a more appropriate forum - perhaps one for java?

Follow on doc(PREQ) not created in teh backend

Hi All,
Need some urgent help...We are runnin on SRM 5.0 n the Classic scneario....
When we order the SC,The backend doc is not created..In the follow on documents...we just get the status as Approved....The workflow is in status completed....Also when I try to execute the functions BBP_REQREQ_TRANSFER and BBP_PD_SC_TRANSFER..Also in BBP_PD tcode...I am getting the final status as i1113--Follow On document created.I get a short DUMP.....I have got a note (859891),...But not sure whether this will solve the problem.....Can anyon please guide me on this????
Regards,
Disha

Disha,
Oki, RFC target is correct now. Check again transaction ST22, SM21 and SM13 in SRM and R/3.
If answers help please don't forget points.
Bertrand

Create po in backend

Similar Messages

Maybe you are looking for