Classic Scenario - SSP PO transfer not happening

Hi Experts,
we are working on SRM 7.0 Classic Scenario, SSP-Classic -SRM 7.0 in PO transfer no error in admin monitor or anywhere but still no PO in backend. Is it XI mandatory for SRM7.0 SSP-Classic PO creation or suggest what could be the problem.
Pl do the needful
Regards,
Mohan

Hi! Thanks for the link. Are you saying that even if I have installed ECC EPH4 but not turned on any of the business function from EPH4 I would still have to install PI? I was looking through the master guide but there was no mention about PI being mandatory and there are no details as to what needs to be done to allow PI to work with SRM. Any idea?
FYI, if I change the system type to ERP_3.0, the PO can be created in ECC.
Regards
SF

Similar Messages

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

PO attachment transfer to ECC - Extended classic scenario

Hi all,
We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to ECC PO?Is this possible in ECS?If so,what are the steps?

HI Alexander,
The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
attachment transfer logic was only implemented in the Classic Scenario.
One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
BADI does (BBP_CREATE_BE_PO_NEW).
We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
1413792 Attachment deleted after changing purchase order
I hope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

Regarding direct material procurement in Classic scenario.

Hello SRM Gurus ,
We are implementing SRM5.0 classic scenario, (SSP with CCM).
As per standard , Shopping cart for a direct material (Requisition for
stock) will create a follow-on document in SRM only (controlled extended
classic scenario).
Client's requirement is that it should create a back-end PR in R/3 system.
Reason being, the client needs to have only one indenting system and one
procurement system.
which BAPI in R/3 for PR/PO has to be used to create PRs or Pos from SRM. Similarly, RFC which FMs have to be used to update status in SRM.
How to bypass the standard replication mechanism.
Please help me..
Thanks and regards,
Mani
mail id : [email protected]

Hi
Why not go for the BADI -> BBP_TARGET_OBJTYPE
Or
Alternatively using SPRO settings, you can change the standard behaviour of the system based on various attrbutes e.g., for a Particular Product, Item category, etc.
Here is the Path ->
IMG -> Supplier Relationship Mnagement -> SRM Server -> Cross-Application Basic settings -> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
Define Objects in Backend System (Purch. Reqs, Reservations,
You perform this step only if you create your Materials Management documents in a backend system.
You specify the documents that are to be created in the backend system for a requirement coverage request.
The following documents can be created:
Purchase requisition
Purchase order
Reservation
You enter a product category (such as office supplies, or hardware) and/or an organizational unit. The organizational unit contains the purchasing group that is responsible for procuring products in this category.
You can enter the product category generically, such as Office*.
Note
The backend system is determined using the product category in the requirement coverage request item. The item also contains the organizatinal unit.
You can use the Business Add-In BBP_TARGET_OBJTYPE if you wish to implement a different logic for creating documents in the backend system.
Example
If purchasing group 01 wants to procure materials from the category Raw Materials, a reservation is to be created every time.
If materials in the category PC are to be procured, a purchase requisition is to be created every time.
Activities
1. Enter the organizational unit and/or the category.
2. Enter a source system.
3. Choose the procurement type.
Reservation if stock is available, otherwise external procurement
The system creates a reservation if the material is subject to inventory management and sufficient stock quantity is available in the warehouse on the requested date.
Always reservation for materials subject to inventory management
The system creates a reservation if the material is subject to inventory management, irrespective of whether stock is available.
Always external procurement
The system does not create a reservation, but always procures the item externally. In this case, you specify the type of external procurement.
The following options are significant if the system cannot create a reservation (for example, if there is no stock available or for a non-stock item) or the system must not create a reservation (choose Always external procurement).
Purchase order if item data complete, otherwise purchase requisition
The system always tries to create a purchase order. If the item data is incomplete (for example, the vendor or price is not known), the system creates a purchase requisition from the item.
Always purchase requisition
The system always creates a purchase requisition.
Always local purchase order
The system always creates a local purchase order.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Classic scenario-Doubts

Hi
I am using IDES(SRM 7.00 withou EHP1) and trying to understand the configuration behind Classic PO.
I have deactivated extended classic scenario and sourcing is not carried out for Product category.PI is not enabled .
I think i have done the necessary configuration required for generating Classic PO and the PO also got generated but i am not able to edit the PO in Backend due to which i am assuming that this PO got transferred from the SRM as the backend PO is not a leading PO
So how can i be sure that the PO which appears in backend is created from Classic scenario and not extended classic scenario.I am not able to edit this PO in backend as i get the message that " BBP Purchase order cannot be changed".
Is the value of field STATU in table EKKO different for PO created from Classic/extended classic scenario.
Thanks

Hi,
the easiest way to find out, which follow-on documents have been created is to check the "Related Documents" tab of the Shopping Cart on the UI ("Document Number" and "Backend Document Number") or the Header/Item links with tc. BBP_PD.
Regards,
Timea

ASN in Extended Classic Scenario with SUS

Hi SRMer?
Is it possible to create an ASN in SUS with Extended Classic Scenario (ECS)?
OSS note 543544 mention that the scenario is limited for document types Purchase Order, Purchase Order Response and Change Order. Confirmations and invoices are not possible. There is no indication on ASNs.
Any help will be appreciated.
Regards.

Hi
Please go through these links ->
SUS-MM Confirmation without ASN
Re: Details on ASN
The specified item was not found.
SUS ASN - mandatory field
ASN Confirmation not created,
Clarifications on EBP-SUS and MM-SUS Scenario
Re: SUS-MM scenario with "POR (order ack.)" and ASN for free text
Creating custom field in ASN screen of SRM SUS
SUS Invoice
Regards
- Atul

Reservation in Classic scenario

Hi Experts,
How does the reservation fucntionality work in classic scenario.
We do not want the application to create a reservationeven if there is stock in the backend. The system should always send the item to sourcing cockpit.
Is there a configuration by which we can restrict Reservation.
Regards,
Jith

Hi Dave,
Many thanks for your inputs. We have already set Always carry out sourcing. But it still does an availability check and tries to create a reservation.
Now we do not want to create reservation at all. We always want to send the item to the sorcing cockpit and create a PO or contract after sourcing.
If we use the BBP_TARGET_OBJECTS BADI we can set the object to resevation and the sourcing indicator is set.
But standard behaviour shoud be not to do a availability check and create reservation, once we set Always carry out sourcing. Is this a bug or are missing any config. (BTW we are on classic scenario).
Regards, Jith

Stock Procurement by Classic Scenario

Hi,
We are using SRM Server 5.5 as an add-on component to ECC 6.0. Only Classic deployment is in our scope.
Can anybody clarify me if we can procure Stock Material by Classic deployment of SRM?
While creating SC, when I click on 'Order as Direct Material' system is unable to determine the Purchasing Group and Org. So its unable to get replicated into R/3.
Thanks
Debashish

Hi Jagdish,
SAP told us that standard Classic scenario can't handle Stock procurement. For stock proc we need to have the extended classic scenario. In Extended classic we have Plan-driven procurement and we can do it there. Once again for stock procurement we need to define Local Purch grp and purch org and we need to have POs in SRM. POs in SRM is possible for Extended Classic scenario and this is not a part of Classic scenario.
SAP said that if we want to create Stock SC in SRM then we have to go for development.
Can anybody in this forum please confirm that in Classic Scenario we can't create a Stock SC (Without development)?
If you refer to OSS note 963000, it says that in ADD-ON SRM , only classic scenario is supported. If this is the case why I can see the 'Order as Direct Material' button.
Can anybody help me here??
Thanks
Debashish

POs are not available in Backend Ext Classic Scenario

Hi All,
Working with SRM 5 and Backend 4.6. in Extended Classic scenario.
For one plant the PO created in the SRM does not get replicated to the Backend whereas for other
Plants it happens.
Any body faced this before,pl give clues.
Thanks & Regards,
Nagarajan

Hi
(1)Is that PO in error in transfer?
(2)Hope you have defined local flag when your defined srm system.
(3) What about communication rfc users profile in both system.
(4) Hope RFC definition and logical system name are same/
BR
Muthu

Urgent ! Purchase Requisition not created in Backend Classic Scenario

Hello All,
I am implementing the classic scenario SRM 5.5. We have replicated the material form the backend to SRM system. Also we have made the necessary config such as maintain backend system, Define Backend System for Product Category, Define Number Ranges for Shopping Carts and Follow-on Document, Define Number Ranges per Backend System for Follow-on Document. Now the problem i am facing is that in the dev system SC with line item with desc and the product (material replicated from backend) as line items are created and their PR is created in the backend. However the same is not happening in the QA system. Only those SC with line item as Desc/text only are created in the backend and those having have product id dont transfer to create PR in the backend. There is no message in the RZ20, SM13, ST22, SM21 etc. Alsowhen i try to tranfer it using the FM BBP_PD_SC_TRANSFER it is created successfully and there is entry in BBP_DOCUMENT_TAB which is cleared afetr clean_reqreq_up is run. I am not sure whats is going wrong. Please help me out guys.
Thanks
Karthik

Hi Andy,
Thanks for the quick responses. I dont see any PR doc no and neither the BUS object type in BBP_PD item details. Please see the o/p below
BE_LOG_SYSTEM                R3QAS400
BE_OBJ_ITEM
BE_OBJECT_TYPE
BE_OBJECT_ID
BE_REFOBJ_TYPE
BE_REFOBJ
BE_REFOBJ_ITEM
BE_REFOBJ_SBITM
BE_REFOBJ_TYPE2
BE_REFOBJ2
BE_REFOBJ_ITEM2
BE_REFOBJ_FYEAR2             0000
BE_STGE_LOC
BE_PLANT                     IE01
BE_BATCH
BE_VAL_TYPE
BE_MOVE_REAS                 0000
BE_EXPERYDATE                000000
BE_PUR_GROUP                 440
BE_PUR_ORG                   IE01
BE_CO_CODE                   IE01
BE_DOC_TYPE                  EC
BE_ACCREQUIRED
BE_SP_STK_IND
BE_INFO_REC
BE_MOVE_TYPE                 101, so i am not sure what could be going wrong.
Is there any way i can debug it and find out what the cause is,
though the calls to the bapis are asynchronous. Also just for the reference sake my backend is 46C. I have been grazing through the notes but haven't found a substantial one.

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

PO is not generated for completed SC in SRM.70 classic scenario.

Hi,
I am working on SRM 7.0 - Classic scenario.
When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process. even we are adding items from catalog.
If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
This is the case even for the SC ordered using catalog materials.
I have checked following configuration and it seems to be ok.
1. 'Define objects in backend system's
2. Number ranges definition in SRM and ECC
3. Document type attribute -BSA in PPOMA_BBP
Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
RZ20 does not show any error for the SC with status I1111.
Is there any sepcial FM to push the SC in SRM 7.0?
Any help/tips would be highly appreciated. Thanks in advance.
Thanks,
Ravi

learnt that PO number has generated in SRM and the same PO number not exist in ECC.
check SM58 , rz20 log or Application monitor for the shopping cart.
or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
let us see .
1. what is the settings in define backend OBJECTS
2. check all basic data in the shopping cart - especially org data
3. run bbp_check_consistancy report for your id?
4. every user has the same issue?
SEE THE RICHARDO technique
http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
Muthu
Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
1480994 How to process a shopping cart with status I1111
Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

PO not generated at backend in classic scenario

Hi,
I am working with SRM 5.0 in classic scenario.
1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
PO - From 3005000000 to 3008000000
2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
PO - From 3004000000 to 3009999999
4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
I see the following description in Admin login:
Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:
PO no. 3005000532 is picked from no. range PO defined in SRM.
But, in SC screen, I do not see any follow-on documents.
When I check BBP_PD, I find following data:
BE_OBJECT_TYPE    -> BUS2012         -> Follow on Document Object Type in backend system
BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
(However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
BE_INFO_REC    -> 5300002566
Also, I can see two lines highlighted in Red under Stats:
                       Status                            Description                 Inactive
HEADER          I1015                         Awaiting Approval                X
0000000001      I1111                    Item in Transfer Process           X
My doubt is that ,
a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
Why there is an error in transmission of PO?
Please help.
thanks

plz see Peter instructions in this thread
SC: Error in transmission BAPI 001
regards
Muthu

Freight is not updated in R/3 in the Extended Classic scenario

Friends,
Freight is not updated in R/3 in the Extended Classic scenario.
Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
We have created a condition for Freight (Value and Percentage)in Create
Payment Conditions using the following menu path:
spro
--> Supplier Relationship Management
--> SRM Server
--> Cross-Application Basic Settings
--> Pricing
--> Process Payment Conditions
When creating a Purchase Order in SRM in the "Item Data" tab, there is
a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
from the drop down menu. Here Freight is available. Add Freight and
the PO record in SRM is updated with the Freight Condition. However,
upon ordering, the Freight condition does not transfer to the PO
recordin R/3.
We've heard this can be achieved by enhancement: only ie by implementing
set of BADIs.. But does anyone know WHICH BADIs we need? Or how we could find out? Thanks.

Hi
 You can either of these BADIs to handlwe the scenario.
BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
BBP_CREATE_PO_BACK OLD Exit while creating a PO in the backend system
BBP_ECS_PO_OUT_BADI ECS: PO Transfer to Logistics Backend
BBP_EXTLOCALPO_BADI Control Extended Classic Scenario
Hope this will help.
Please reward suitable points.
Regards
- Atul

Classic Scenario - SSP PO transfer not happening

Similar Messages

Maybe you are looking for