BADI BBP_DETERMINE_LOGSYS

Hi,
What does BADI BBP_DETERMINE_LOGSYS do.
Please let me know the steps to implement the same anthe usage as well.
Thanks,
Manu

method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE.
DATA: ls_partner TYPE bbp_pds_partner,
        ls_ORG      type bbp_pds_org.
use the purchase org to determine if the document should be sent
to a backend system
read table IT_ORG into ls_org index 1.
if ls_org-proc_org_id = '50000027'.
    cv_logsys = 'QW8CLNT250'.
elseif ls_org-proc_org_id = '50000953'.
    cv_logsys = 'QPTCLNT100'.
endif.
endmethod.
OR :
method IF_EX_BBP_DETERMINE_LOGSYS~DETERMINE_LOGSYS.
data: ztprod type zprod1.
data result(4).
data tline TYPE LINE OF bbpt_detlogsys_item.
loop at item_data into tline.
   case sy-uname.
      when 'BUYER3'.
         if tline-product eq '69E2D3C8AF4B5C4CBDCC73A50C58EFA2' or
           tline-product eq '6BB856ADA25D584FA0B5A2FDCDA27766' or
           tline-product eq 'F31AD68E8EDCE646A9C7ECC4F24CE464' or
           tline-product eq 'ABC0320E1A37E743B75406DF0B7C53BF' or
           tline-product eq '3C0665006B2D2A43B3A1CC74B560E8A9' or
           tline-product eq '8F97635441496647A69CD021A5FFF4D2'.
           tline-be_co_code = '1000'.
           tline-logical_system = 'F47CLNT800'.
           tline-BE_PUR_ORG = 'O 50000660'.
           tline-BE_PUR_GROUP = 'O 50000662'.
           modify item_data from tline.
         endif.
      when others.
           select single * from zprod1 into ztprod where product eq tline-product.
           if sy-subrc eq 0.
             tline-be_co_code = '3000'.
             tline-logical_system = 'F47CLNT800'.
             modify item_data from tline.
           elseif tline-product is initial.
             tline-be_co_code = '3000'.
             tline-logical_system = 'F47CLNT800'.
             tline-BE_PUR_ORG = 'O 50000612'.
             tline-BE_PUR_GROUP = 'O 50000614'.
             modify item_data from tline.
           endif.
   endcase.
endloop.
endmethod.
copied from SRM wiki.

Similar Messages

Any Badi required for service procurement scenario?

Dear Guru's
I am configuring the service procurement classic scenario in SRM 7.01. Our requirement is as below:
If the service requisition has backend contract available as a source of supply, it will create a purchase order in the backend ERP system.
However, when it comes to contract, service hierarchy is supported in the srm contract as well. So, unlike srm 7.0, we can create follow-on contract with service hierarchy both in SAP SRM system and backend ERP system. How the system will decide whether to create the contract in the backend system or local SRM system?
If I want to create local contract only from the purchase requisitions with service hierarchy, do I need to take help of the BAdi 'BBP_DETERMINE_LOGSYS'? Or i Need the BAdi only if I need to create the contract directly in the backend system.
Secondly, Will the local contract be available as a source of supply in the sourcing cockpit or only the backend contract will be available as a sourcing?
Thanks in advance,
Ranjan
Ranjan Sutradhar

Dear Ricardo,
Thanks for the confirmation. Till SRM 7.0, service hierarchy was not supported in the contract document in SRM. The system behaviour is to create contract with service hierarchy in the backend system. In case of multiple backend systems, we need to use the BAdi 'BBP_DETERMINE_LOGSYS'.
Since we are in the SRM 7.01 where the central contract supports service hierarchy, we are proceeding with the approach suggested by you.
Thanks and regards,
Ranjan

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

Error in Sourcing Cockpit

Hi Gurus,
we're working with EC Scenario in SRM 4.0 and Sourcing Cockpit.
We can create the following documents from a shopping cart: Bid Invitation, Auction and Purchase Order, but not a Contract. The system goes exits out and dumps the following messages:
"Note
The following error text was processed in the system SV5 : Transaction type ECPO must not be used for object type BUS2000113
The error occurred on the application server itsv03_SV5_10 and in the work process
The termination type was: TH_RES_FREE
The ABAP call stack was:
      Form: ADD_MESSAGES_TO_LOG of program SAPLBBP_SOCO_APP
      Form: CREATE_FOLLOW_ON_DOCUMENT of program SAPLBBP_SOCO_APP
      Function: BBP_SOCO_EV_FOLLOW_ON_CREATE of program SAPLBBP_SOCO_APP
      Function: BBP_SOCO_EVENT_DISPATCHER of program SAPLBBP_SOCO_APP
      Form: FCODE of program SAPLBBP_SOCO_UI_ITS
      Module: FCODE of program SAPLBBP_SOCO_UI_ITS"
Could u help us?
Thx, Enrico

Hello Enrico,
Please maintain the transaction type for the BO/TransCat- BUS2000113 in the SPRO at the path SRM Server -> Cross-Application Basic Settings->Define Transaction Types and also if you have implemented the Badi BBP_DETERMINE_LOGSYS , please verify the code for the method ~CONTRACT_LOGSYS_DETERMINE.
hope this info will be useful.
regards,
Mani

Distribution of purchase contracts from SRM4.0 to ERP 2004

Hello all,
Any body has experience in distributing Purchase contract from SRM to R/3.
i have activated BADIs
BBP_DETERMINE_LOGSYS;BBP_CTR_BE_CREATE in SRM and BBP_CTR in R/3.
Right now i can create contracts in EBP,but i unable to transfer them to backend.
Until now i have followed the documentation stategic sourcing configuration guide.
Please give your valuble information to distribute service contracts.
Thanking you,
Mahesh Madasu.

Hi Mahesh,
If you are using classic scenario then try these:
Go to Table: BBP_DOCUMENT_TAB. Check whether your contract no.
Then go to T. Code: WE20 in Backend system.
Check for the Partner TYPE of you backend system in Partner profiile.
Go to classification TAB. And check the partner status is Activate or not. The status should be 'A'. Check the inbound Parameter BLAORD is present or not.
Then go to YOur SRM system and go to WE20 and activate the partner status by setting the parameter to 'A'. Then redo the processes.
This may help you.
Regards,
Charles

Master Data coming from 1 backend and GOA distributed to many bakends

Hello,
In our case (using SRM 5.0) one backend system is used to replicate all material master data and GOA will be distributed to multiple backends including the one that is used for master data. As far as i know the logical backend system is determined through materials/material groups while GOA is distributed. In the above case how can we intervene with this logic to be able to distribute the GOA to whatever backend we have, even though if the MD is not coming from them?
Thank you,

Hi,
You can use the BADI BBP_DETERMINE_LOGSYS for this purpose.
The method :CONTRACT_LOGSYS_DETERMINE (Determine Target System of Contract) has been provided for the same purpose.
Sample BADI Implementation at SDN Wiki:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/srm/bbp_determine_logsys-contract_logsys_determine&
Regards
Kathirvel
Edited by: Kathirvel Balakrishnan on Feb 25, 2008 1:00 PM

Creation of backend contract from SRM system?

Dear Experts,
I am bit confused with the scenario of creation of backend contract from SAP SRM system? It says in few cases, based on the BAdi 'BBP_DETERMINE_Logsys', the system creates a backned contract directly in a backend ERP system. Why do we need when we have central contract?
We can meet the same requirement through central contract where we will authorize only purchasing organizations of a backend system and block the contract for local sourcing in SRM?
Secondly, How to find a contract / scheduling agreement created in a backend system when a central contract is distributed to the backend system?
Thanks and regards,
Ranjan

Hello Ranjan
question on contracts?
Note 1476307 - Importing parameter not filled in BADI BBP_DETERMINE_LOGSYS
in classic scenario , The Business wanted to create a contract from cockpit or via BID
this BADI helps
Symptom
You have implemented BAdi BBP_DETERMINE_LOGSYS to control the system in which contract is created in following scenarios:
1. Creation of contract from an accepted quote / bid.
2. Creation of contract from a requisition in SOCO.
In the method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE of the BAdi implementation, importing parameter IT_ORG doesnot have any values.
Other terms
Backend contract
Reason and Prerequisites
some business wants to create a backend contract from SRM . see some Dinesh Powale / Claude threads for more understanding.
Muthu

Global Outline Agreement Distribution

Hello,
i try to distribute global outline agreement ( transaction type GCTR ) from SRM 4.0 to ERP 2004.
But I can´t find in my browser ( its service = bbp_ctr_main ) the header data "Distribution".
I see in my header data only following taps:
Basic Data / Documtents / Conditions / Output Logs / Status / Approval Preview
I set up following things till now:
- IDoc type = BLAREL02 as Inbound Processing in SRM System
- IDoc type = BLAREL02 as Outbound Processing in Backend System
- transaction type = GCTR with internale number range in SRM System
- transaction type = GCTR with external number range in Backend System
- BADI: BBP_CTR_BE_CREATE in Method: CONTRACT_PROCESS_TYPE_FILL
   EV_PROCESS_TYPE = 'GCTR'.
- BADI: BBP_DETERMINE_LOGSYS in Method: CONTRACT_LOGSYS_DETERMINE
   CV_LOGSYS = 'our Backend System'.
- PPOMA_BBP - Attributes; Tab: Function -under Local I mapped the Purchasing Organisation and the
   Purchasing Group with Backend System
*Which customizing is still missed to see this tab "Distribution" in the header data?!
Would be glad if someone could help.
Best Regards
J.F.

If you really want to do GOA, you've got the wrong service (CTR_MAINCC is the one you are looking for). The role stratpurchaser* has both transactions: contract and global outline.
BBP_DETERMINE_LOGSYS does not need to be implemented, BBP_CTR_CREATE_BE neither (maybe for condition mapping!).
You are missing blaord for replication to ECC from SRM, you are missing BBP_SRV if you want to make GOA for services.
Along the way you will probably find that some other things need to be customised in ECC (setting up of global company, some other minor stuff like company code that's missing in ECC).
So basically you don't miss any customising for seeing the tab, but for replicating GOA you DO miss something.
In the Wiki section for SRM on this site you can find the configuration guide for setting up of contracts and GOAs, if you follow that you will have done around 90-95% of all necessary steps.
Regards,
Robin

SRM 7.01 Backend Contracts creation with XI/PI ESOA Service

Hello, we are implementing SRM 7.01 PPS with Extended Classic Scenario. We need to create contracts backend contracts ( ECC) from RFX RESPONSE at SRM. As we have ECC 6.0 EHP 5 we have to use Esoa services. The problem is that we have set up PI but no contract is created at ECC ( not even in SRM) when we pressed button " create contracts" from rfx response even thought the message at SRM is " contracts XXXXXX created" I think we are missing some customizing in ECC.
We have already implemented badi BBP_DETERMINE_LOGSYS
I read note 1268821 who explains that we have to activate business function LOG_MM_P2PSE_1 in ECC but I think this only apply for "CENTRAL CONTRACTS" and we dont want to use central contracts. We just want to creates contracts at ECC from rfx response in SRM. I couldn´t find any documentation about this, just for Central Contracts or backend contracts creation (through idocs) . Any idea?
Thanks in advance for your help!
Best Regards
Liam

The first interface that try to get out from SRM was " PurchasingContractERPRequest_Out_V1", thus based on this interface we made the configuration on PI. So, after pressing button " create contract" on srm if we execute tx SXI_MONITOR in SRM we found the interface " PurchasingContractERPRequest_Out_V1" and in the backend system ( ECC) at tv SXI_MONITOR we found interface PurchasingContractERPRequest_In_V1 for this contract with black and white flag ( processed successfully) but no contract created in ECC not even SRM.
Anyway we have checked that inbound proxy is executed but we dont see any contract created
Is this the right Interface? We are missing something?
Best regads and thanks again for your help!

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
Regards
- Atul

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

Workflow Error Purchase Order

Hi Experts,
my issue is the following: We try to create a purchase order in SRM with a local mapped category (mapped to the local srm system) and depending on the user the target system should be overwritten in BADI bbp_determine_logsys to get the purchase order in the respective backend.
The idea is to use all categories centrally and map them depending on the purchasers origin country.
The question is that ...
If we map the category to the backend system of the purchaser and try to transfer the purchase order, there will be no error (not in RZ20 or anything) - of course also the direct way with the FU bbp_procdoc_tansfer will work.
If we map the category as it should be to the local srm system - the workflow transfer won't work anymore and we got an error message in RZ20 with the following text: Error reading the export data for EXEC transfer of purchase order <PO No.>.
The very strange thing is, that even in this case with the FU bbp_procdoc_transfer the purchase order can be transferred to the backend of the respective user and it will switch the locally mapped backend to the purchaser / users one.
Could anyone imagine what might be a problem - is there any check in the workflow itself what raises the exception and aborts the workflow.
Thanks for your help.
Cheers,
Timo

I am not sure if this is gonna help you..
Note 1154122 - BBP_POC : Backend Data validation from SRM
Regards,
PR.

Enhancement for PO creation in EBP

Hi ,
When I create a PO and shopping cart in EBP,the Goods recepient is not transferred to R/3.
Can anyone suggest a proper user-exit/BADI to transfer this to R/3 while creating PO in EBP?
Thanks,
Sandip.

Hi Sandeep,
Are you using Extended Classic scenario ?
There are few BAdIs available and can be used for it.
Normally, if it Extended Classic scenario, PO is replicated in R/3. If it is a local scenario, PO is created in SRM.
There is a BAdI which is responsible for Switching on / off Extended Classic Scenario.
BBP_EXTLOCALPO_BADI
Also there may be requirement to change Logical System. Use BAdI BBP_DETERMINE_LOGSYS for this.
If you have any question related to Shopping Cart Workflow ( Header Based or Itembased) / Contract Workflow, please drop me a mail.
Thanks and Warm Regards.
Pras Durafe

Product-ID mandatory in RFQ and Contract

Hi SRM-gurus. Is Product-ID (material master) mandatory in order to create Quotations and Contracts from Sourcing? Also, can you create backend contract without material master and/or item category "W", or are there any limitations related to contract generation from Sourcing to ERP?`
brgs ziggy

Hi Jain
1) Suggest you to replicate materials. Refer Blog by Marcin /people/marcin.gajewski/blog/2007/02/05/how-to-replicate-material-master-from-r3-to-srm
2) If you want to create contract in ECC from sourcing (or RFx), you need to implement BADI BBP_DETERMINE_LOGSYS. Check the sample implementation at https://wiki.sdn.sap.com/wiki/display/SRM/BBP_DETERMINE_LOGSYS-CONTRACT_LOGSYS_DETERMINE (if there is any problem with this link, goto SRM Wiki section in SDN)
3) You need to follow 'Contract Management Scenario' and 'Plan Driven Procurement' config, if you have Solution manager.
If you do not have solution manager, use 'Sourcing Config Guide' given in https://wiki.sdn.sap.com/wiki/display/SRM/Configuration+Guides (or service.sap.com/ibc-srm).
Best regards
Ramki

Direct contract in the backend - Classic Scenery SRM 7.0

Hi Masters,
I´m using SRM 7.0 Package 08 in the classic scenery.
I´m trying to create a direct contract of a QUOT acepted and that need to go to the backend.
I´m using two badis:
BBP_DETERMINE_LOGSYS
Where the variable CV_LOGSYS is with the system backend destiny
BBP_CTR_BE_CREATE
Where the variable IV_LOGICAL_SYSTEM is with the system backend destiny.
Where the variable CV_USER is with the user RFC.
The result is generating myself a message: " CONTRACT 4400000041 - WAS CREATED " (/SAPSRM/PDO_WKL455 BPP_PD455)
But that contract is not available in SRM and it is not also available in ECC.
I forgetting something?
Thank you,
Pedro Marques

I believe that it exists yes possibility, as well as it comments on the text of the badi:
Use
With Business Add-In BBP_CTR_BE_CREATE, you can replace or supplement existing contract data in SAP Enterprise Buyer with your own backend structures and tables.
Enterprise Buyer calls this BAdI before it makes the RFC to the backend system to create a contract.
Activities
Implement and activate the BAdI if you wish to create contracts in the backend system and replace or supplement contract data.
Anybody have some idea?
Thanks,
Pedro

BADI BBP_DETERMINE_LOGSYS

Similar Messages

Maybe you are looking for