Extended classic scenario local PO
Hi All ,
Need some inputs on the extended classic scenario local PO.
There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
We can change the same PO from the process purchase order also.
But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
If sy-uname = WF_BATCH
Do the mapping part
Endif,
But I donu2019t think so; this logic will work all the times.
Please can anyone give me some pointer for the same, it will be really helpful for me .
Seeking your help on this
Thank you,
Hi Latha,
This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
Hope you can build your logic based on this; this is a better logic on par with the existing one.
Regards
Kathirvel
Similar Messages
-
Extended classic scenario local PO Output status
Hello all ,
Need some inputs on extended classic scenario local PO Output.
My requirement is , when ever the put get process successfully in SRM , I need to send a mail to requester saying that u201C for this particular output got processed successfully u201C
I have business requirement, we need to run this report every 30 min, This report has to pull out the all the PO number from the current time to past 30 min, for the output got processed successfully.
To meet this requirement, I am using the output log entry table PPFTTRIGG where we can see the all the PO with the status and time stamp also.
But some how, this table maintaining incorrect time stamp.
Ex: If I create PO, process the PO output, and if I see the time stamp for this PO, its showing as 10 min before the current time.
Did anybody come across this issue? Or can anybody suggest me any alternative approach for this.
I mean is there any function module/ table available, which will give PO Output status also.
Can you please give me any pointers for this?
Seeking your help on this.
Wish you a advance happy new year.
Thank you.Hi Latha,
Did you have a look at the standard report RSPPFPROCESS. For PO's please pass the below selection screen values along with the appropiate date & time details:
Application = BBP_PD
Action Profile = BBP_PD_PO
Then regarding the time difference, please make sure that the application server time is sync with the actual time of the time-zone. This could also be a reason.
Then what you can do is to clone the RSPPFPROCESS program and add the email notification logic on that.
Please have a look at the BADI BBP_PROCESS_PO, this can be of some help for your requirement.
Hope this solves your problem.
Regards
Kathirvel -
Completion workflow in extended classic scenario
Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
PatríciaHi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth -
Extended Classic Scenario-Replication of Local PO to R/3 fails
Hi,
In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
Can anyone suggest if we are missing anything.
Regards
garuguHello,
this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
Rgds
Christophe -
GOA + Local Contract distribution to R/3 in Extended Classic Scenario
Dear SRM Gurus,
System Information: SRM Server 5.5 EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ??? Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!! -
PO error - extended classic scenario
Hi Guys,
I'm using SRM 5.0 with extended classic scenario...
During creation of the purchase order locally (in SRM) I got the "error in process" status.
My means of T-code RZ20 I got the following info to ithis error:
context:B2B Procurement
object name:Purchase Order
short name: Backend application errors
status: Active
Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
using Transaction BBP_PD I got the following status:
Status: I1080
Description: in transfer to execution system
Do you have any idea what should I do in order to resolve this outstanding issue?
many thanks in advance for your help.
regards,
PiotrekHi
Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
<b>Meanwhile, try the following SAP OSS Notes as well -></b>
<u>Note 508972 - Error during transfer of extended purchase orders
Note 881650 - Duplicate transfer/output of the purchase order
PO status in " error In Process ".
Error in Transfer Process (Urgent )
FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
Hope this will help.
Regards
- Atul -
PO output for Extended classic Scenario from the R/3 backend
Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DVHi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh -
SRM: Extended Classic scenario: Request your help.
Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador -
SR_ Extended Classic Scenario : Request your help please
Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.Hi ,
Go to SPRO
There is a node - Activate Extended Classic scenario
Do the config.
Regards
G.Ganesh Kumar -
Classic Scenanio and Extended Classic Scenario
Hi all,
I would implement on the same system 2 different scenario:
1. Classic Scenario for self service procurement
2. Extended Classic Scenario for the following business scenario:
a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
Can coexist this different scenario?
Can I address this different scenario only with organizational differences?
Thanks
Bye
MarcoHi Marco,
I see 2 quick ways to realise your requirement.
The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI you have to write the logic to retrieve and compare this.
Keep in mind that these are user-based distinctions and not based on scenario. -
Organization structure in extended classic scenario
Hi All
I am trying to configure extended classic scenario on SAP SRM 7.0. I have made the following settings for the same:
1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
I have a few doubts.
1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds I'll have to leave blank. plz suggest
2. Also is IPC configuration mandatory for extended classic scenario
Plz give your suggestion on above mentioned issue
Regards
Pawan Keshwani
Edited by: pawankeshwani on Mar 18, 2011 8:33 AMHi Pawan,
No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
Regards,
Nikhil -
Payment term key with limit days in Extended Classic Scenario
Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
ZTERM ZTAGG
K180 09
K180 19
K180 31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
ZTERM ZTAGG
E000 00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regardshi,
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. -
'BAPI_POEC_CREATE' function doesn't work with extended classic scenario
Hi everybody.
Antecedents:
We are working in an extended classic scenario.
When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
But when we execute BAPI_POEC_CREATE function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
Both exampled were created with exactly same data (partners, items, categories, accounts, )
Moreover when we modify the second PO created via ITS, the systems doesnt show any error message, we can order our PO again without error, but the PO isnt replicate in the ERP system.
1. We executed BAPI_POEC_GETDETAIL function module, and there is only a difference between POs, E_PO_STATUS table.
PO created by transaction has 8 entries:
I1009 X
I1015 X
I1021
I1038
I1039 X
I1043
I1080 X
I1180
And PO created by BAPI has 5 entries:
I1015 X
I1021
I1038
I1043
I1180
2. We run BBP_PD transaction, and there is only a difference.
PO created by transaction mode shows:
- Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
And PO created by BAPI
- Message: No Messages
Could anyone help me with the problem?
Thanks in advance.
Raúl.Hi Raúl,
this is exact, BAPI_POEC_CREATE is designed to create local PO.
If you want to replicate it to R/3, then you have to change it to an ECS PO.
In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
- change header subtype to EP
- change header log system to SRM (keep FI LS as is)
- determine a backend purch group & org
- complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
- ... and maybe other R/3 relevant fields
Compare both PO one by one, and adapt the gaps.
Rgds
Christophe
PS: please reward points for helpfull answers -
Extended Classic Scenario PPOMA_Purchasing Org and Group
Hi gurus,
We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.
In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.
Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.
The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.
The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.
Any help on this? It's because of the version?
Many thanks and regards,
I will give Points!Hi Ana
PURCH_GRP Purchasing group Number of an organizational unit that is indicated as local purchasing group in the organizational plan.
This attribute is simulated. You define an organizational unit as company on the Function tab.
PURCH_GRPX R/3 purchasing group Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.
This attribute is simulated. You define the ID and the associated system on the Function tab.
PURCH_ORG Purchasing organization Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.
This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
PURCH_ORGX R/3 purchasing organization Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.
This attribute is simulated. You define the ID and the associated system on the Function tab.
can you elaborate more?
in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.
there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up
regards
Muthu
regards
Muthu -
Extended Classic Scenario - how does the integration work ?
Hi,
Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?
Many thanks,
fionaHi Olaf,
I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
The Extended classic scenario only refers to the local PO creation replicated in R/3.
In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
Regards.
Vadim
Maybe you are looking for
-
C# - Acrobat 9.4.5 - PrintPages not responsive
I've been stuck on an issue for a month or so, and running out of ideas. I'm trying to use the Acrobat API's "PrintPages" method to print a PDF document. I'm able to load the PDFs in my WinForm just fine, populate their fields, etc. But whenever I in
-
OLAP Variable with user exit for Infopackage Selection 0fiscper
Hi Frds/ Guru's , I have a requirement to use a OLAP Variable for Fiscal year period 0fiscper(Characteristic ) in the Infopackage Selection. . I need to extract the data for Previous Year and Current Year , that is to be automatically
-
Urgent - Big POC: SAP Adapter Java API !
Hi, I'm trying to get from an SAP BAPPI values using SAP Adapter Java API. I had tested at BEA and it worked fine. the code is: try { InitialContext ic = new InitialContext(env); // Create an object that provides the services established during confi
-
I am at a loss. I am trying to send XML using a URLLoader when the request is sent via navigateToUrl i get the Post data but when using a Loader nothing. Any help is appreciated.
-
How Can I install Oracle 10g R1 Linux x86 on Red Hat Enterprise 6
I have tried so many times to install Oracle 10g R1 10.1.0.3 on the Red Hat Enterprise Linux 6 x86_64 but just its appear to be imposible, The Installer failed on the linking and make process. i need to know if anyone has been installed the Oracle 10