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

Similar Messages

SES Release Strategy not invoked in Backend from SRM confirmation posting

Hi,
I have configured a SES release strategy based on vendor number in R/3. When a SES is created in R/3 via ML81N the release strategy is invoked as expected. However, when a confirmation is entered in SRM for that vendor, the SES that is created in the backend system is created in accepted status and the release strategy is not invoked.
Can anyone advise how to get this to work the same way as ML81N?
I would expect that the SES would be created in the backend from the confirmation without acceptance and the release procedure to be the same as ML81N.
thanks,
Michelle.

Hi,
The SRM confirmation in EBP is the goods receipt(MIGO) and not the service entry sheet entry (ML81N) as we do in Materials management.
As per my understanding there is no provision of service entry sheet entry in SRM 5.0 as of now and SRM 7.0 has this option coming up :
In SRM 7.0 ,
"Supplier-maintained confirmation (service entry sheet) for services performed based on the service items within a purchase order
Confirmation supporting hierarchical structure of service items"
are added.
Look for this information in the thread which speaks about SRM 7.0
Re: Benefits of upgrading to SAP SRM 2007
which gives the info in slide 11, Delta SRM 7.0, Service procurement -2
Best regards,
Sridhar.

Sending shopping cart no from SRM to ECC while creating PO in ECC from SRM

Hi all,
I have a requirement where in i need to enhance the custom screen of PO. In this custom screen there is a field called shopping cart number.
So when a PO is created in SRM the shopping cart has to be copied into this custom field of ECC.
i got to know that BBP_CREATE_BE_PO_NEW is to be used.
So please enlighten me on how to implement this badi?
Thanks and Regards
Veda

Hi Veda,
Please go through the following Wiki link to know more about BBP_CREATE_BE_PO_NEW usage to send customer fields:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/bbp_create_be_po_new-CreatePOin+backend
Thanks,
Pradeep

To invoke tax procedure from SRM

Hi Guru's
We are using SRM ECS and our backend is connected to TAXWARE. Can you please let me know how to invoke TAX Procedure/Pricing Procedure in backend from SRM. If you can list the BAPI's, FM, RFC's that would be helpful.
Thanks in advance
Deepu.

closed

Creation of multiple contracts in ERP backend from 1 GOA in SRM

Hello fellow SRM'ers, we are on SRM 5.5 and we have a scenario where we create a GOA in SRM and it get's created as a contract in the ERP backend system. This is working fine. Now our client would like to have multiple contracts created in the backend, one for each company when the GOA is saved. I found OSS note 646903, statement #2 that explains how to code the badi bbp_ctr, but is this all that is required to do this? It seems to me that the code in BBP_CTR will only create 1 contract/idoc. Can anyone tell me how we generate an idoc/contract that we want to create in ERP backend? Or is this how it's done?
Points will be rewarded for usefull answers. I have read most of the posts on this forum and have not found any answers yet.
Thanks,
Marty

Hi,
Please go through the below explanation from SAP documentation which says the no of contracts that would be created in the backend depends on
--If you activate grouping logic for locations in GOA from SPRO under cross aplication settings, items belonging to the same release-authorized purchasing organization, but different locations, can be grouped together into one backend contract. This requires a 1:1:1 relationship between an item, the release-authorized purchasing organization, and the location. This means that for each item, you can only assign one release-authorized purchasing organization, and one location, in order to release the GOA.
If you do not select this indicator to activate the grouping logic for location, a separate backend contract is created for each item belonging to the same release-authorized purchasing organization, but with different locations. Only items referring to the same release-authorized purchasing organization and location can be combined into one backend contract.---
So the bottomline is by default, when we distribute one separate contract is created for each location.
Hope this clarifies.
Regards,
RRK

Tax code determination when a PO is created from SRM

Hi Experts
I am using extended classic SRM 7.0
When a PO is transferred to the SAP backend system, sometimes the TAX code is different from what was supplied in FM BBP_PO_INBOUND.
It looks like; tax code determination in backend system determines a different code and does not use the tax code supplied when PO is created.
Is there a way to override this tax determination in backend system so that it uses the Tax code supplied rather than determine a tax code that is different?
This seems to be a problem when a new PO is created because when I change the PO and this sent again, the backend system is updated correctly with the Tax code supplied from SRM.
I hope some has come across this type of situation and can suggest something.
Regards

I put your HTML page (TEST2.html) and CSS file (body_new.css) on my server and it looks OK.
http://www.ossiningdesignguild.com/TEST2.html
It's possible your web server is not properly configured and sends a Content-Type HTTP header that says text/plain instead of text/css for your style sheet file.
If you're using Apache, have your server admin check the httpd.conf file for MIME type settings.
Should they need assistance, send them here:
http://httpd.apache.org/docs/2.2/configuring.html
This is not a problem with your main site since the CSS is embedded, rather than remote.
I'll call you after lunch.
Ken

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

Creation of backend contract from SRM system?

Dear Experts,
I am bit confused with the scenario of creation of backend contract from SAP SRM system? It says in few cases, based on the BAdi 'BBP_DETERMINE_Logsys', the system creates a backned contract directly in a backend ERP system. Why do we need when we have central contract?
We can meet the same requirement through central contract where we will authorize only purchasing organizations of a backend system and block the contract for local sourcing in SRM?
Secondly, How to find a contract / scheduling agreement created in a backend system when a central contract is distributed to the backend system?
Thanks and regards,
Ranjan

Hello Ranjan
question on contracts?
Note 1476307 - Importing parameter not filled in BADI BBP_DETERMINE_LOGSYS
in classic scenario , The Business wanted to create a contract from cockpit or via BID
this BADI helps
Symptom
You have implemented BAdi BBP_DETERMINE_LOGSYS to control the system in which contract is created in following scenarios:
1. Creation of contract from an accepted quote / bid.
2. Creation of contract from a requisition in SOCO.
In the method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE of the BAdi implementation, importing parameter IT_ORG doesnot have any values.
Other terms
Backend contract
Reason and Prerequisites
some business wants to create a backend contract from SRM . see some Dinesh Powale / Claude threads for more understanding.
Muthu

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.
<b>Pls reward points for useful answers.</b>

PO:Error in Process while transferring to backend (ECC 6.0) from SRM 5.0

Hi folks,
We are on an Extended Classic Scenario. We have a major problem occurring in Production system only for the the limit orders. Limit Orders are not getting transferred to ECC 6.0 from SRM (Error in Process clearly shows the non existence for PO created first time)
I also know that Error in Process/ Transfer Failed status comes up for several causes.
This was working fine for months together, suddenly this problem is coming up. 1 Week back we had a Patch Upgrade too. I have checked the Vendor data, Account Assignment and other Basic data too and everything looks fine. We have tried debugging the FM's on SRM side which transfers the PO(ex:BBP_PD_PO_TRANSFER_EXEC_V2)
After debugging too we are not able to rectify from where the error is coming up..
I need your valuable inputs on this.
Thanks a lot in advance.

Thanks a lot on your Key inputs Peter.
I just forgot to mention one more thing, i.e., in RZ20 (SRM) we could see the following errors for limit orders:
(01) PurchOrder 003....012: Transfer failed
(02) PurchOrder 003....012: Please maintain services or limits
(03) PurchOrder 003....012: Purchase order still contains faulty items
(04) PO 003....012: No instance of object type PurchaseOrder has been created. External reference
To trace the issue backwards we tried creating a limit order PO directly from ECC backend (ME21N Transaction)
One thing we could observe is in Limit tab if we not specify Expected Value and Overall Limit we are encountering the same error as shown up in RZ20.
This gave us a vague idea that the price is not getting transferred for Limit Orders from SRM 5.0 to ECC 6.0 backend. Any key inputs on specific FM etc.,to debug and see what value is getting transferred from SRM to ECC would come handy.
I hope Peter and others will help me on this.

PO release/distribution (from SRM to backend) FModules?

Hi experts,
I need to create a report that allows the user to release/distribute (sorry if these are not the right words to call the process) a PO ... My report actually retrieves the header of the purchase order ,that has status "waiting" ("park") in SRM (a change version)... so, given the header, is there a FM to release easily the po ?
(excuse the terminology, I'm not sure that's correct: I talk about release/distribute a PO meaning the process that brings a correct po from SRM to the backend).

Hi sanjeev, tried your solution without success. I get an error message, BBP_PD381.... I call the FM in this way:
CALL FUNCTION 'BBP_PD_PO_STATUS_CHANGE_WF'
EXPORTING
iv_guid = srm_change_header_guid
iv_status = 1
where srm_change_header_guid is the header's guid of the change version on my PO, the one I'd like to release.
Some infos from debugging.... the error comes from the call function that follows:
CALL FUNCTION 'CRM_STATUS_CHANGE_FOR_ACTIVITY'
(source report: LBBP_PDF0Y)
values of the parameters in debug are:
check_only = X;
client = sy-mandt;
objnr = p_new_guid (which is the guid of the header of the change version)
vrgng = 'RELP'
XNOAUTO = 'X'.
The message is hard to translate in english, anyway says something like "error on modify state RELP. "Release purchase order not allowed".
Any hint?
Thanks in advance.

PO on R/3 not created from SRM Bid

Hello,
I create a contract on R/3 from a bid without problem but when i try a PO it is created only on SRM.
I´m using classical scenario, i define the backend system on
IF_EX_BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS
using
loop at item_data into line.
line-logical_system = 'BACCLNT202'.
line-logsys_fi = 'BACCLNT202'.
modify item_data from line.
endloop.
I implemeted bapi BBP_CREATE_BE_PO_NEW and BBP_CREATE_PO_BACK but the program dont go through them.
Do i miss some customizing??
Regards,

Hi,
We are having a very similar problem.
We have used the BADI BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE.
If you look at the documentation for this it says:
"In the standard system, the system creates contracts locally from Sourcing and SAP Bidding Engine You can use this BAdI to determine a backend system. The local system used by the standard system to create contracts is XYZ4711. In the field CV_LOGSYS, you enter the logical system ABC0815 that links to a backend system. In this way, contracts are created in the backend system."
Based on this information we put the following code in this BADI:
CV_LOGSYS = 'CSC_Q01030'.
But it still appears as though the system is trying to create a local PO.
When we goto SM21 we see the following error:
BBP_PD 396 Purchase orders cannot be created without IPC pricing
This indicates that the SRM system is still trying to create a backend document or a local purchase order. We are using the classic scenario (not extended classic) and want a backend R/3 document.
Can you check SM21 in your system as well as look at the METHOD that we have used and try it in your system? Please let me know if any of this information helps or if you find another solution, maybe we can trade notes and resolve both of our issues!
Regards,
-Paul

IDOC from SRM to create Down Payment Request (F-47) in ECC

We need to build one custom object in SRM. This object(upon final approval) should trigger the creation of Down Payment Request in ECC(Tcode F-47) System. To elaborate more in simplest terms, The custom object in SRM is created to capture Advance Payment Request related Data. (Vendor, contract no, Advance Amount etc...). There is no standard IDOC type in SRM to capture this data.
In ECC system, we have one standard IDOC related to Down payment request (IDOC Type FIDCCP01).
Other thing is, when this outbound IDOC is trigerred from SRM, it has to not only to get the data from that custom object but also calculate some values and fill this in down payment request fields.
Now questions:
Please help in letting me know the best method to achieve this. Should we use IDOC tecnology? If yes, then please detail the steps needed to achive this. Should we create the same IDOCbasic type FIDCCP01 in SRM as we have in ECC. How can IDOC capture the calculated values for some fields in Down payment request? Do we need to create some function module for this?
Please detail the process step needed to achive this(like IDOC Basic Type creation, Functiona Module creation etc etc...). Or if we should use some other methd like RFC or BAdi etc... then please let know.
Thanks for any help the SDN community could provide.
Regards,
Ravi
Edited by: Ravi Gandhi on Oct 9, 2011 10:16 AM
Edited by: Ravi Gandhi on Oct 9, 2011 10:23 AM

Dear Ravi,
Did you have a answer for this case?
i need to create IDOC for F-47 and i need the program to use.
Here we have a IDOC for FB01 only.
tks
Marco Magri

Attachment not seen in PO created from SRM SC

Hi,
We try to send attachments from SRM shopping cart to Back end R/3. This attachment has to be captured in PO item.
But it does not appear there. We have made all relevant configurations.
When i search for the attachment in CV02N i can find the document created with the attachment and link is there between the document and the PO number.
Even when the DMS document is attached to the PO manually and then viewed again in the PO through ME23N i could not find the attachment.
I have made the same set of configurations in ECC6 and it appears to work fine.
regards
R.Rajesh

Hello,
Please check note 668062. Also make sure you have the most recent Java-Applet installed (note 1034072).
Kind regards,
Gaurav
PLEASE GIVE POINTS FOR USEFUL REPLIES

Vendor replication from SUS to ECC 6 backend in SRM 7.01

Dear Gurus,
1. Vendor registration in ROS: Vendor's are registered in ROS and stay there as preapproved vendors. They can be replicated to SRM system through OPI calls. How these suppliers are replicated to backend MM system?
2. I get to know that from SRM 7 enhpk 1 facilitates transfer of vendor data from SRM SUS to SAP ERP. A business partner monitor cockpit is available in SUS/ROS. Do we need to upgrade our ECC system to ECC 6.0 enhpk 5 or ECC 6.0 enhpk 4 will do to avail these functionality?
Any input on these will be highly appreciated.
Thanks and regards,
Ranjan

Hi Ranjan,
As of now without Ehp1, vendors are replicated to backend MM systems using a PI scenario "Supply_base_management".
And you are right, from Ehp1 vendor replication will be handled as you mentioned and ECC Ehp4 will support that.
Nikhil

Create PO at backend from SRM

Similar Messages

Maybe you are looking for