Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
Please go through the SAP OSS Notes below ->
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
Do let me know.
Regards
- Atul

Similar Messages

Purchase order replication – extended classic scenario using XML proxy via PI

Hi Experts
Question:
In case of extended classic deployment is it possible to use XML proxy to
transfer SRM purchase orders to ECC? As we know as of SRM 7.01 its via RFC
whether SRM 7.02 onwards does SAP support XML for ECS too?
Has
anyone read about this in any of the SAP forums?
Background: In our project, client have invested
heavily on XI and XI monitoring and troubleshooting, integrated to SAP SOLMAN.
And would like to opt for XML mode of transfer and reuse existing solution.
This is the main reason we would like to be very clear in our understanding
before we go back to client.
We appreciate your time and support.
Regards
Prashanth

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

Extended Classic Scenario - Can Purchase Requsition be created in R/3?

Hi SRM Gurus,
In Extended Classic Scenario, Is it possible to have Purchase Req to be created in the backend?
Technically whether it is possible or not? Functionally, there is no such need, I agree.
Thanks & Regards,
Ramkumar

Hi
Please confirm what sceanrio in SRM are you planning for ?
I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE" -> I guess, it's possible, but not sure. Try it out.
Purchase Order (PO) will be created in the R/3 system using the BADI - BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
Regards
- Atul

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

PO status Held in extended classic scenario

Hello SRM gurus,
         I am very new to SRM with MM background. I have a question which i think you guys might have come across earlier.
We are using version 5.5 extended classic scenario, replicated all the vendors and materials from R/3 to SRM, did all the basic configuration needed, we are able to see those vendors and materials in SRM also. here is the issue. we are trying to add an item to the shopping cart which in turn creates a PO in SRM so that it automatically replicates in R/3. But the PO status in SRM is Held and we found out that vendor is not assigned to the PO which is very clear why the PO has been held. So what could be reason the vendor is not getting assigned to the PO though we have the inforecord and source list(checked the fix indicator also)for the same material and vendor in R/3 ?
I'm sure many of u would have come across this issue. please help me out.

Hi Satya
      Thanks for your quick response.
1) We are using Workflow without approval process
2) I checked BBP_NUM_SUSPO in SRM server. There is nothing in there. Is this the correct number range for PO? I checked OMH6 in R/3. please tell me how to sync it.
   When we try to post it after editing the PO with vendor number, we are getting Waiting for approval error though we have activated Without workflow approval process. let me know why is it showing that error?
We have another strange issue which is, We have assigned a material say M01 to a pur.group P01,Pur.org POrg1 and vendor V01 and have info record and source list, but we don't see this Pur.grp when we create the shopping cart and it defaults to some other pur.grp say AP01 which we deleted long back. can you tell me where it is picking up the deleted ones?
thanks
Pradheep.

Partner functions OA and IP missing for Vendor in Extended classic PO

As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

Hi
Which SRM Server are you using ?
You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.
Here is the Path from SPRO Transaction ->
Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions
Maintain Similar entries as mentioned below.
Function Function Type Usage Description Abbreviation
00000016 0013 B2B Requester RQ
00000017 0007 B2B Contact Person CP
00000018 0011 B2B Bidder BI
00000019 0012 B2B Vendor VD
00000020 0002 B2B Goods Recipient GR
00000025 0014 B2B Portal Provider PP
00000026 0008 B2B Responsible Employee RE
00000027 0017 B2B Ship-To Address DP
00000028 0003 B2B Invoice Recipient IR
00000029 0015 B2B Invoicing Party IP
00000030 0018 B2B Ship-From Address SP
00000034 0002 B2B Plant PLNT
00000038 0001 B2B Sold-to Party ORDR
00000039 0026 B2B Preferred Vendor PRVD
00000051 0019 B2B Purch. Org. Auth. For Release AREL
00000074 0025 B2B Service Agent SERV
00000075 0031 B2B Location LOCA
00000097 0034 B2B Invoicing Party Employee IPEm
Hope this will definitely help.
More details ->
For 1), see these links below ->
Partner function missing in backend PO
Re: Error in transmission while PO cration
"Multiple" partner data at PO header
Partner functions in plan driven MM-SUS
Re: Partner function not found
Number range for business partner
Re: Problem with BP. Assignment: Business partner person to user not unique
Error in creation of Employee for Business Partner
Re: enter exactly one partner of type vendor
Re: Business partner as Vendor and Invoicing Party
Partner functions in EBP for extended Classic Scenario
Classic Scenario PO has multiple OA Partner Functions for Vendor
For 2), see the pointers ->
There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.
In SRM, there is no standard relation betwwen plant and vendor master data.
You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.
Replication of Ordering Address from R/3 to SRM
Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
Partner function Payee in SRM
Adding Partner Function to R/3 PO from SRM in Classic using BADI
Do let me know.
Regards
- Atul

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,
Piotrek

Hi
Go to transaction - SPAM to get all the required Patch levels and other required system version details.
Meanwhile, try the following SAP OSS Notes as well ->
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)
Hope this will help.
Regards
- Atul

No GR on Confirmation Approval in Extended Classic Scenario

Hi all gurus out there,
We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
Cheers!
Siow Fong

Hi Guys,
I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
Regards
Siow Fong

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

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
garugu

Hello,
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

Attachment transfer of PO from SRM to Back end for extended classic scenario

Hi Experts,
We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
Thanks ,
Aishwarya.M

As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario
http://scn.sap.com/thread/1873708
Also I suggest you should debug and see if its sending attachment from SRM if yes then
could be something missing at ECC side , To debug use this
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
Are you configuring this for the 1 st time or its an error which u encountered?
You must raise a NOte to SAP for the same till a solution is found .
This one is another which you can check ..
http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

Extended Classic Scenario - PO Update issue

Hello experts.
We are working with SRM 5 in the extended classic scenario and we have a serious problem in a productive environment for the following case.
(01) We create a purchase requisition (PR) in R/3 with several items;
(02) We send PR to the SRM generating a shopping cart;
(03) The buyer creates a PO for all items from the shopping cart;
(04) The PO is transmitted to R/3;
(05) For some cases buyer changes the PO wich is sent back (updated) to R/3;
So far so good. The problem happens when some item in the request already has GR or Invoice. In those cases when the PO is updated on SRM, its transmission to R/3 does not occur, generating an error log that can be seen in transaction RZ20 of SRM.
I understand that if any GR or Invoice exists for the item it can no longer be modified, but is it expected that no other item can also be modified from SRM? What is the expected behavior for this case?
Moreover, even if the GR and Invoice have been canceled, we are still unable to update the PO in R/3 from SRM. Is this a expected behavior? It was our understanding that the PO should be updated if all incoming documents (GR, Invoice, SES ..) were completely canceled.
We appreciate any help on this matter.
Thanks and Regards,
Evandro Miasato

Hi, Masa,
Thank you for your advice,
I set the method U:Print Using Berkeley Protocol, after that
in trx. SP01 I have the Error Status on Composite Document -
Status Incorrect (Reason Unknown).
Best regards,
Guzal.

Tolerance key DQ in extended Classic scenario give Backen error message

Dear all,
I am using SRM 7.0, SP 9
Extended Classic Scenario.
I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
I also set up the ECC tolerances:
- Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
- And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
And even with this set up I still get the error message
u201CBackend Purchase Order quantity exceeded by 1 EAu201D
when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
What Configuration am I missing?
Cheers
Ulrike

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

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

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Similar Messages

Maybe you are looking for