SRM 7.0 PO document type

Hi,
In SRM 7.0, how is the transaction type for the PO decided.
I know it is ECPO for Indirect PO's
and ECDP for Direct PO materials.
Pls let me know, how the transaction type is decided.
because, whenver I create a PO, the number range is chosen from ECDP and not from ECPO.
Though I dont use a material in my PO, I just create a account assigned PO.
I had set the attribute BSA as : ECPO in SRM Root node and it applies to all.
Regards
harish

(tr:SPRO)
SAP Supplier Relationship Management
SRM Server
Cross-Application Basic Settings
Define Transaction Types
Trying to set BP : on FM BBP_GET_PROCTYPE_FROM_PUR and check.
I can't check this due to limited authorizations.
You can use BADI BBP_DOC_CHANGE_BADI to change the BE_DOC_TYPE for your items.
Regards
Lauren

Similar Messages

Mapping of invoice document type in SRM and Backend

hi,
I need to map invoice document type in SRM and backend. We are in SRM5.0.
e.g. when we create no PO invoice , we need to select document type from drop down and that document type should be replicated to backend invoice document type.
1. There is no list in drop down of invoice document type ( RE/RN)
2. How it will be replicated to back end document type when enter document type instead of selection?
If anyone came across this, pls let me know.
regards,
Rahul Mandale

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

PO's Document type created from Shopping Cart

Hi all,
I work on a SRM 5 system with Extend classic scenario.
when I create a PO from a SC, the system assign automatically a document type.
I have to change this assignment.
I already define transaction type for BUS2201, but I'm not able to find where the assigned doc type from SC is.
Thanks
Enzo

Hi Enzo,
The P.O in SRM has document type has either ECPO or ECDP.
These document types are assigned in the attributes of the root org.
The attributes you maintain in the root org for document types are :
BSA & DP_PROC_TY
You can find the possible document types in SPRO > IMG > SRM > SRM Server > Cross Application basic settings > Define Transaction types
Choose BUS2201 (Transaction category) and click on the Transaction types in the Dialog Structure on the left side. There you can see ECDP & ECPO transaction types.
Hope this makes you more clear. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Document Types for PR created in R/3

WE are implementing SRM classic scenario and in version 4.0.
WE are creating the Purchase requisition in R/3 systems.
Now in R/3 we have 2 document types PR01 for Materials and PR02 for services.
There is a badi BBP_SC_TRansfer_BE with method Group_RQ which can be used to
segregate the document types PR01 for material and PR02 for services.
However how do I maintaion the number ranges as in SRM we have only one field where we can maintain the number ranges in cutomising for
Define Number Ranges per Backend System for Follow-on Documents Here it allows only one Attribute for Purchase Requistion.
How do I maintain the number ranges in R/3 as external number ranges for the 2 document types PR01 and Pr02.
Currently I have maintained RQ for Pr01 as external no ranges in R/3.
Is it that I have to maintain RQ for PR02 also or if separate number range than how do I assgin in SRM.
Can any one thorw light on this.
Regards,
Nimish Sheth

Dear Vadim
In Srm we have faclity of maintaining one no range only
In R/3 I have 2 no ranges for Document type PR01(Materials) and PR02(Services)
Is it that I have to keep a common number range with 2 document type in R/3.
IN SRM                         IN R/3
No range                       NO range
RQ - Internl Numbers PR01      RQ - External (PR01)
                               AB - External for PR02
Now how do I map AB in SRM .
or Keep RQ for PR01 and PR02 in R/3
Can you pls throw light on this.
Regards,
Nimish Sheth

New document type for shopping cart /PO

Hi Gurus,
I have created a new transaction type ZSHC for Shopping carts in SRM. I have given it a new number range.
while creating a shopping cart , how do i ensure that my shopping carts get created with this transaction type?
is there any attribute which controls this ?
Regards,
Mangesh

Thanks Shrini for your response.
BADI "BBP_CREATE_BE_PO_NEW" does not exist in SRM 4.0. The corresponds BADI in SRM 4.0 is "BBP_CREATE_PO_BACK".
The documentation of this BADI says that it can be used to change all data TRANSFERRED TO THE BACKEND SYSTEM to create a purchase order.
I would want the document type to be selected when the PO is created in SRM and not when SRM transfers the PO to the backend. Because in that case I fear that SRM can have one doucment type and R/3 would end up having different document type for same PO.
I will activate the BADI and keep the thread posted.
Thanks
Venkatesh

Which document type for special PO

Hi,
Which document type should be used if I want to select all receipts on the purchase order placed by an external vendor?
/Marc

Hi,
If your question is correct and if I understand it correctly, you are asking about a document type of PO, used by a Vendor to create for you...and receipts of such POs generated....To find receipts of such document, you wanted document type....if this is correct, it could be one of the follwoing:
1) Either you have a work around solution if you are using standard SAP R/3 or ECC
So, in your project there may be a document type created to let the vendor create POs for you ....for which there must be a document type created...that you only can track it...to track it, there are many ways...you may find those out from first EKKO using user ID provided to external vendors to create POs for you.....Then run those PO#s from the result in ME2N or ME2k etc...by selecting appropriate selection parameters...(for example WE101)
2) If you are using SCM solution of SAP, it may be supplier collaboration hub
3) SUS - Supplier Self Service of SRM.....
In all the above cases, you can still find the result as explained in STEP#1 above
Regards

PO - Document Type FO and Item Category B - Can they be transferred to SUS?

Hi SDN
We are using R/3 4.7 with SRM 5.0 - Classic Scenario and XI 4.0. We are just about to launch an SUS project to put our PO's on SUS for our suppliers. Our organization is dealing with PO's for both Goods and Services. As we know that there are no problems about putting the GR-Type PO's (NB type) on SUS but I would like to know if it is possible to transfer PO's that would be from the Document Type FO and Item Category B (Blanket PO) to SUS and ensure that our suppliers can do the entire PO Acknowledgement, PO Change and post the Invoice via SUS. If not, what are the options for our R/3 - SUS installation?
Thanks!
Eric L.
Edited by: Eric Longpré on Apr 23, 2009 12:57 PM

Hi,
This has been discussed several times on this FORUM..Pls refer the foll threads for more details:
PR document type in the back end system
Change "Document Type in R/3 System" in SC
Changing document type of PO backend
Re: Change PO number/document type
BR,
Disha.
Do reward points for useful answers.

PO document type selection

Hi Experts,
SRM 7 EHP 1
ECC 6 EHP 5
PPS through CPPR (classic scenario)
Purchasers create RFx and receive bids against the RFx. Once the bid is accepted, PO is to be awarded.
We want to have an option of selecting the ECC PO document types while creating the PO through 'Create Purchase Order' option in the bid. We have maintained the ECC PO document types in the org. structure against BSA attribute but still do not get an option of selecting the document type.
Please advise.
Thanks & Regards,
Amish

Hi Amish,
You are trying to run PPS (Procurement for Public Sector) in Classic Scenario.
PPS is only supported in ECS(Extended Classic Scenario.Hence this scenario will not be possible.
For more details refer http://help.sap.com/saphelp_srm70/helpdata/en/c9/8d47ed4a5548c08521615d84a590e6/content.htm
Hope this helps.
Best Regards,
Vinita

Multiple PO document types/transaction types in Extended Classic scenario

Hi All,
We are on SRM_SERVER 550, Extended Classic Scenario.
We have a requirement where we need to create multiple PO document types (based on certain criteria).
I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
We need more document types and these should be triggerred automatically after SC is approved.
I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
I have 2 specific questions:
1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
Regards,
Srivatsan

Srivatsan,
To create new transaction type:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
To create new number range:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
Rgs,
Pedro Marques

BBP_BS_GROUP_BE for new document type and number range

Hi gurus,
I am working on Classic scenario in SRM and currently have used the above BADI to use a different document type and number range when creating the PO in the backend system. It all works fine. The only thing is I noticed that the BE_DOC_TYPE field in the shopping cart is still reflected as 'EC' even though the PO created in ECC is for example EC1. My question: Is this standard SRM? If so, is it common to leave this field as it is or is it advisable for us to change the document type to EC1 as well? Also, is there any implication in standard SRM reporting and downstream processes that you are aware of?
Appreciate any advice on the above.
Cheers!
Sf

We have ended up having to populate the document type on a custom field or alternatively replace the existing one.

Influence PO document type in ECC from Sourcing Cockpit in Classic Scenario

Hello experts: we are running SRM 7.0 with ECC 6 EhP 4 in a classic scenario.
Our business requirements are: all SC item created with reference to a catalogue item must result in a PO not subject to release strategy in ECC6 MM. For this purpose, document type ZEC has been entered under parameter BSA in tcode PPOMA_BBP.
Due to Sourcing customizing, some Shopping carts items without source of supply are sent to Sourcing Cockpit.
In sourcing cockpit application, buyer completes the open items by including the vendor, price, etc and create draft POs that are finally converted into backend purchase orders in ECC6. These Purchase orders, created without reference to a catalogue item should be subject to release strategy and approved by the corresponding approval body in ECC6.
Due to that, we must change the document type in backend and enter another one which is subject to release strategy. We tried it thru badi BBP_TARGET_OBJTYPE but we could not get it. we change BE_DOC_TYPE to NB when the catalog id is blank in the SC item and follow-doc is PO. However, system always creates PO with document type ZEC
We would like to know how to influence the PO document type when we are trying to create POs from SOCO.
Any clue about it?
Many thanks in advance
Best Regards
Valentí

Solved

Document type and Transaction type

Hi,
Can someone give me a clear and detailed understanding of how to maintain transaction types in SRM system and document types in the backend system based on various scenarios (i.e standalone,classic. extended.....)
Is it mandatory that the document type assigned in org plan attribute BSA be maintained in the local system as well??
Thanks
sunny

Lol Sunny,
Thanks for the compliment, but no, I'm in france. I work on SRM for now 5 years, so it helps
In fact META BAPI are only BAPIs, with a certain way of developping: What SAP calls "Abstraction Layer".
This allow you to manage Partner system version differences, and backend unavailability, the process is:
->META_BAPI
-First try synchronously
-->Read table BBP_FUNCTION_MAP (and now get into BADI) to get the exact function module to be called depending on the partner system type and its version
--->Call of this function (which either makes local actions, or call the backend system with RFC)
If the system was unable to call the partner system , it creates a job to re-try the call (based on what you entered in customizing).
Here is the SAP description:
- Depending on the release level used, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the back end system. The abstraction layer encapsulates the BAPI calls in the back end system that are necessary to generate the back end documents from requirement coverage requests. The abstraction layer accesses the following sources of information:
-Dispatcher: This function module analyzes the Customizing settings and then knows:
-- Which driver it must call
-- Which back end system it is communicating with
-- The back end system release
-- Driver: For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back end system.
-- Spoolers: The spooler controls the transfer of documents from the Enterprise Buyer system to the back end system. If errors occur during the transfer, for example, the back end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back end system at regular intervals and to transfer the documents.
Regards.
Vadim.
PS if you are really "amazed" please be more generous in your rewards

Can we have two document types in SAP_SRM5.0?

Hi All,
Can we have two document types in SAP_SRM5.0? The doc type EC is configured for EC-PR and PO , But now we need to rollout buyers intervenes if sc< 5000K, should generate the PO directly for non-catalog.
For instance;
1. Existing scenario,
a. SC ->approval u2013>PR then buyer converts into PO manually (Non-Catalog).
b. SC( with catalog )->approval->PO ( 54XXXX )
2. Now as per our requirement, SC->approval -> PO ( non-catalog ).
How to cope up these two scenarios in our system.
Please advice?
Regards,
Lalit

Hi Masa,
Itu2019s true we have classic scenario and there is no difference in these two scenario; we simply need to pressure off of low value of SC has to converted into PO directly.
We have set EC doc type ( no range as Internal here SRM and In Backend System External with No Range 54 XXXX ) .
We donu2019t need to create new number range;
1. No Range : 51 XXX
SC->PR-PO ( 51xxxxx) range ( Existing System)
SC ( less thn 1000k ) only PO ( with the same number range 51XXXX) ( proposed )
2. No Range 54 XXXX which we have set for Catalog PO which I donu2019t want to disturb .
Please advice how we can proceed .
Regards,
Lalit

Creating a new PR document type in SPRO

I am presently doing over the Release strategy for PRs within our company but there are some new departments to be added.
I need to create new PR doucment types for these new departments,how do i do this?
I am presently in SPRO,pathway Purchasing>Purchase Requisition>Release Procedure>Set up procedure with classification>release strategy.
Transaction OMGQ. How do i create a PR type for a new department,
e.g.Decision Support Services will need a PR type ZDEC to be created.
Any ideas ppl?
Thanks

Hi
Have you replicated the Same document type rom R/3 into the SRM system.
Are you using Extended Classic Scenario (ECS) ?
The solution proposed in this post won't work in your case:
Using the BADI BBP_TARGET_OBJECTS to determine the backend doc type will only allow you to determine the follow-on doc type for each SC item: RS or PR or PO.
With this BADI, you set 1, 2 or 3 in ITEM_DATA-OBJ_TO_GEN.
But it does not provide you with the choice of the R/3 doc type (PR01 or PR02) for each "follow-on" doc type (PR).
There is a BADI to change de backend Doc type or the backend doc number: BBP_SC_TRANSFER_BE Determine Number Ranges and Grouping in Backend Documents
You can, independent of the standard, use the method GROUP_RQ to create a separate grouping for purchase requisitions.
In the standard, the system creates only one purchase requisition in the backend for all purchase requisitions with the same backend document type . If the document types are different, the standard creates a separate purchase requisition for each document type.
So you can use this BADI and its method GROUP_RQ to group material items in one side, and service items on the other side.
Please go through the link for more details ->

Document Types for PR created in R/3
Do let me know.
Regards
- Atul

Non PO invoice : Entry of document types

Hi,
I am working on SRM5.0 with EC scenario. Client needs to perform invoice / credit memo with document type. We cant select document type from drop down box at header level. How to replicate backend invoice document type (RE gross invoice, RN net invoice, etc) to SRM? Any report to execute for it?
Thanks in advance.
Rahul Mandale

Hi Yann,
Client need to create SRM invocie without PO but with different document type and should create corresponding accounting documents in backend.
In SRM SPRO, it is mentioned that "For invoice verification, you can only set RE as the document type for posting gross in the backend system.You can also set another document type using a user exit in the backend. This also has to be flagged as gross document type."
Which user exit will help here to get Idoc inbound parameter to create different document type RE, AE, AA etc. ?
Let me know if you had came across such requirement.
regards,
Rahul Mandale

SRM 7.0 PO document type

Similar Messages

Maybe you are looking for