Activate extended-classic by badi -- PO not created in ECC

Hi,
in certain circumstances I activate the extended-classic escenario in SOCO using Badi BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS:
'logical_system = 'ECCSYSTEM'.
I do this because i need to launch the PO workflow in SRM for the PO created in the SOCO. The problem is the PO is created with the 'saved' status, not in 'order' status, and also when it approves such requests are not replicated to ECC.
If i change the scenario with the BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO Badi I have no problem, the PO is created with 'order' status and when i approved the PO is replicated inmediately in ECC.
Any idea about this problem?
The scenario is classic in srm 7 with ehp8.
Thanks.

Hi,
I would believe the configuration is not properly done in your system.
The BADI BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO is the only BADI you can used to adjust if ECS PO will be created.
By using the BADI BBP_DETERMINE_LOGSYS, it has instead lead to a SRM local PO is requested for and this PO will never replicated to the ERP. If you are not requiring it, please leave this BADI completely.
ECS PO will always be ordered when the PO information is complete. It will be HELD status when the information is incomplete. If you encountered HELD status, it means a purchaser has to complete those missing information first before the ECS PO can be saved. Do you have some customer fields that are mandatory but not populated in the SOCO creation and this lead to HELD status?
Regards.
YS

Similar Messages

Activate extended classic scenario

Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
Extended local PO
BE Purch Grps Resp.
Back-end check reqd
Back-end errors, show as error msg
Which options may I have to select?
Thanks in advance

Hi,
I think Rosa's requirement is to create a manual and local contract in SRM. Indeed you mentioned an excellent BADi, but my understanding is this badi gets called from the sourcing application. I am not sure whether this gets called from the SRM local contract. This is the help documentation I am pasting here. It would be wonderful if this works. See the highlighted "importing parameters" part of the following pasted one.
Thank you,
DV
Determine Target System of Contract
Use
With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
Requirements
You are using a backend system with Release 4.6B or higher.
You have created the logical system in activity Define Logical System
Parameters
Importing
The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
IT_HEADER
Header structures
IT_ITEMS
Item structures
IT_PARTNER
Business partner data such as vendor or location
IT_ORG
Organizational data
Changing
In the method you can overwrite the following field:
CV_LOGSYS
Name of the system in which a contract is to be created.
If this field remains empty or contains the name of the local system, then the contract is created locally.
If this field contains the name of a backend system, then the contract is created there.
Notes
When coding the method, use the delivered sample coding as a guide.
See also
BAdI Determine Backend System / Company Code

PO not creating in ECC

Hi All,
We are facing a problem in SRM production system. The PO is created in SRM after approval completion. Now the PO is not creating in ECC prod system. We are getting the following error in SRM EBP.
Comm. error checking account assignmt for purchase order 4100001309 in system HCPCLNT100
How does the PO replicate to ECC system?Is there any place to see where is the log?
Please help as this is very high priorit

Hi,
You can check if the PO in question was not transferred due to an internal error or check why the error is happening in backend system. In order to do it, you can perform the following action:
- Breakpoint at FM B46B_DPO_TRANSFER;
- SE37 BBP_PD_PO_TRANSFER_EXEC, enter PO header GUID and execute;
- Program will stop at FM where the BP was set;
- Look for statement CALL FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination;
- F6 or F5 to debug into ERP (2nd session will start). Here you can check the table lt_bapi_return in order to check if the PO has been created or not in backend.
I hope it helps.
Kind regards,
Ricardo

SRM PO not created in ECC

Hi All,
We are facing a problem in SRM production system. The PO is created in SRM after approval completion. Now the PO is not creating in ECC prod system. We are getting the following error in SRM EBP.
Comm. error checking account assignmt for purchase order 4100001309 in system HCPCLNT100
How does the PO replicate to ECC system?Is there any place to see where is the log?
Please help as this is very high priority.
Reg,
Bis

Hello Bis,
Try to re-send PO to backend using application monitor in WEBGUI.
If it does not solve your problem, create a new PO with same PO type and account assignment data, but directly in R/3 backend: you will get R/3 error. It should give you clues.
Regards.
Laurent.

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

Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

Control extended classic mode BADI

Hi,
I am trying to setup the system to work in the extended classic scenario.
I have activated the extended classic switch and i am using the BADI control extended classic badi.
For product categories that i want to use in extended classic mode, the logic inside the BADI returns a "X"
For Eg: I have a product cat "Boards" for whcih the BADI returns "X"
When i add this pruduct category to my shopping cart, there is a dump in ITS.
However, I remove the product cat "Board" from the BADI, I am able to add this product cat to the shopping cart without a dump.
Please let me know why this is happening.
Dump:
Runtime Errors           UNCAUGHT_EXCEPTION
Except.                  CX_BBP_PD_ABORT
Date and Time            04/21/2010   06:07:37
Short dump has not been completely stored (too big)
What happened?
The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
       along
the call hierarchy.
Since exceptions represent error situations and this error was not
      adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be
      terminated.
Please help
Thnaks,
Vignesh

Hi Laurent,
I am getting the foloowing error. Can you identify what is going on ?
Information on where terminated
    Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT".
    The main program was "SAPLBBP_SC_UI_ITS ".
    In the source code you have the termination point in line 73
    of the (Include) program "LBBP_PDHU08".
Source Code Extract
Line SourceCde
   43
   44   READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.
   45   CONCATENATE   '/' ls_callstack2-eventtype
   46                 ls_callstack2-eventname ls_callstack2-progname
   47                 INTO lv_msgarg3 SEPARATED BY space.
   48
   49   CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'
   50     EXPORTING
   51       msgid   = gc_msgid_bbp_pd
   52       msgno   = 047
   53       msgarg1 = lv_msgarg1
   54       msgarg2 = lv_msgarg2
   55       msgarg3 = lv_msgarg3.
   56
   57   MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no
   58           WITH ls_callstack1-eventtype
   59                ls_callstack1-eventname
   60                ls_callstack1-progname.
   61
   62   rollback work.
   63
   64 * get the messages from the application log
   65   TRY.
   66       CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'
   67         TABLES
   68           e_messages = lt_messages.
   69     CATCH cx_bbp_pd_abort.
   70       REFRESH lt_messages.
   71   ENDTRY.
   72
>>>>>   RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING
   74       worked_on_document = lv_guid
   75       t100_msgid = gc_msgid_bbp_pd
   76       t100_msgno = iv_msg_no
   77       t_appl_log_messages = lt_messages.
   78
   79 ENDFUNCTION.
Pls help

Extended Classic: Only local Purchase Order Creating

We are using SRM 7.0 SP5 extended classic scenario. The local purchase order is creating but the ERP PO is not creating. There are no errors in RZ20, ST22 or SLG1.
I can't even tell if it is trying to create a backend document. I set a break in the CREATE_DOCUMENT method where the BAP_PO_CREATE1 FM is called but the break never gets hit.

Azad,
Thanks for your answer. I did not realize that in exteneded classic the local PO is created first and that the backend po only gets created once PO has been sent out.
For anyone else having this problem this is what I found:
When I edit the local PO and order the PO after fixing an output problem, (PO is setup for no approval) , I was then able to see the backend errors appear on the PO infoming me of what when wrong when the sytem attempted to create the ERP PO.
Also, you can debug from program B46B_DPO_TRANSFER...set a break on line 393, just before the BBP_PO_INBOUND function module is called. Also that function module in the ERP system calls the BBP_PO_CREATE1 BAPI.
All this information has helped me answer my question....thanks for everyones help!
Edited by: Paul Trauth on Jan 27, 2010 5:24 PM

SRM Extended Classic SC Attachments to PO documents in ECC

Hi Experts,
We are attempting to pass attachments using extended classic with the BAPI_DOCUMENT_CREATE2 in the ECS PO out badi. We have been unsuccessful so far. Does anyohne has a solution for this?
Many Thanks,
Paul

Hi Ravindra,
Yes, we are trying to attach to the item level. The same as when you use the classic scenario. Since it is not supported in the extended classic scenario we are trying to do it ourselfs in the po out badi used for extneded classic.
Regards,
-Paul

Migrated BADI Implementation not triggering in ECC 6.0

Hi Experts,
Need your urgent assistance how to deal with migrated BADI implementation which is not triggering in ECC 6.0. This is for PO (ME_PROCESS_PO_CUST). In the original version (4.6) it was working fine. But when this is migrated to ECC 6.0, it's not firing. Please help to trigger this one in ECC 6.0.
Points will be awarded and thanks in advance,
LM

Hi LM,
Can you just paste the code in the BADI.(The method in which code is there)
Is this BADI implemented and in the Active status.
Check in SE19 if the implementation exist or not?
There may be chances that some condition is not met which can trigger this BADI. Have you read the documentation of the BADI?
Regards,
Atish

Classic scenario: po is not created

hai ,
i am using classic scenario.In define backend objects configuration i made the following settings
product category purchasing group internal procurement external procurement
555 555 always external proc create po if data is complete
when i created shopping cart it always creates purchase requisition in the back end.i have checked in shopping cart.delivery date,price ,quantity,account section,and source of supply .everthing is fine but in the backend pr is created instead of purchase order .how can i find out the solution.can anyone suggest me regarding the above problem
thanks and regards
chakradhar

(1)there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
(From peter thread copied)
(2)BBP_TARGET_OBJECTS BADi active in your system?
(3) Do you have fixed source of supply in your sc ?
555 555 always external proc create po if data is complete ? what is this 555 555
do you given corrrect material group / purcase group correcly...
regards
muthu

Note 543544 - SUS: Extended Classic Scenario for EBP not supported

Hi,
I am trying to get more information on SUS implemenation with ECS, I am aware of this note 543544 and its limitations for ECS in creating invoices and confirmations. But I wanted to know if any one has implemented SUS with ECS and also created invoices in SUS.
Please share your ideas.
Thanks,
Sreedhar

Our scenario is, SRM 5.5, ECS, Confirmations and Invoicing in SRM.
So, I am trying to analyze if MM-SUS or SRM-SUS will be a goo fit for us. But I came across note "543544 - SUS:ECS for EBP not supported" and I am trying to figure out what would be the best way to implement SUS.
Option # 1: If I implement SRM-SUS - I can do POR, PO changes and all PO related activity without conf and invoices. I am not worried about confirmations, our requirement for SUS invoicing is a must. So is there any way to achieve this as is or with IMS?
Option # 2: MM-SUS, but how to do this? since the leading PO, conf and invoicing all are done currently in SRM.
Please share your ideas.
Thanks,
Sreedhar

Document number range not creating in Ecc 6.0

Hi
I have tried creating document number range in 6.0, but the change interval buttion is in display mode and not in the change mode, so not able to cretae number range. Any input.
Urgent please help.

Hi Sidhu,
It could be the limit of the authorization.
So try to check whether you have an authorizatin to change the interval or not.
Hope it helps.

Shopping Cart replication using Extended Classic?

Dear Experts,
I was wondering if there is a BADI that I could possbily use to replicate SRM shopping carts to ECC Purchase Requisitions using the Extended Classic scenario.
Thanks in advance,
Mark

Hi Mark,
in case of extended classic scenario you can not create purchase requisition (the basic of this scenario, that you create at first the local PO, then this will be replicated into the backend system).
Therefore I would suggest to activate the BAdI BBP_EXTLOCALPO_BADI. With this BAdI you can choose between classic and extended classic scenario depending on your business logic (and create ECC PO or purchase requisition).
E.g. depending on the product category:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
clear: bbp_extpo_gl-bbpexpo,
          bbp_extpo_gl-mandt.
data: cat_guid type COMT_CATEGORY_GUID,
          category type COMT_CATEGORY.
cat_guid = ITEM_DATA-CATEGORY.
CALL FUNCTION 'COM_CATEGORY_READ'
    EXPORTING
      iv_category_guid = cat_guid
    IMPORTING
      es_category      = category
    EXCEPTIONS
      OTHERS           = 0.
if
* category XYZ
     category-CATEGORY_ID EQ 'XYZ'.
     bbp_extpo_gl-bbpexpo = 'X'.
     bbp_extpo_gl-mandt   = sy-mandt.
    return.
endif.
endmethod.
Regards,
Peter

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

Activate extended-classic by badi -- PO not created in ECC

Similar Messages

Maybe you are looking for