Central Contract Header Message

Hi,
I created an enhancement for contract replication in PI. I generated the proxy in SRM and I could see the fields. I then implemented BADI /sapsrm/bd_soa_mapping (method map_xi_to_backend) to map the fields. The problem is that the new fields are not in this method.
Is there something I'm doing wrong?

Hi Mathweus,
AFAIK - You need to enhance the BADI to process custom fields.
regards,
Harish

Similar Messages

Custom Condition in Header of central contract

Dear All,
SAP SRM 7.02. Service Contract.
I have created the custom condition type and added those in the group 0100 & 01HD for contract in SRM with reference to ECC.
The custom condition is displayed at header level in the dropdown list. But when i choose the custom conditions, it is not selecting. Where as the standard condition type is selected and able to enter discount.
Kindly guide me .Is there any other setting need to be maintained...??
thank you...

HI,
Now it is displayed in central contract in SRM and i have created contract in SRM and Send to ECC with header custom condition to ECC system.
In the ECC the contract is created, but the central contract that is created in ECC, where i can see the Header condition. I can able to see the Item conditions.
Since the central contract screen in ECC is different than normal contract screen in ECC system.
Thank you...

Central Contract SRM

I have an issue, when I create central contract in SRM. The Select System is empty. No values is there on the screen.
Even though I try to create contract I have the error message "No customizing entry for SRDCLNT600 in table BBP_BACKEND_DEST"
We have SRM 7.0 , ECC 6.0 EHP4.
Regards,
Lya

Hi,
Are you just setting up the system or has it been working already ?
Pl check your "Define Backend Systems" set-up in IMG. There might be some problem here.
Best regards,
Ramki

SRM 7.0 Central Contract- Distribution to backend failure

Hello experts,
We are implementing SRM 7.0 Central contracts scenario with PI.
The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
We checked all the configuration settings (including the PI settings) and everything seems to be in order.
Would appreciate if someone could throw some light on the potential cause of the problem.
Thanks
Raman.

Message must have created . check all SRM outbound transactions .but PI could not catch them.
Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
The sap stratergy in earlier version
table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
like any reference of your input must register in one ECC table but there may have this table or some other reference table.
/SAPSRM/CL_CH_SOA_MAP_CTR_OUT CLASS DO SOME trick and see what is happening here
Muthu

SRM 7.0 Central Contracts Excel upload

Hello All,
We are implementing SRM7.0 implementing Central Contracts ,want to use the Contract upload function using the excel file , not able to see the button or link to do the same .
Am i missing something.
Pl. help.
Cheers,
Sid

Hello Jay,
I would like to import central contract to SRM 7.0 via excel file. When I click the import button after edit functionality and choose the file path from the computer and push the upload, button, I got an error message saying File type of specified file C:\Users\Administrator\Desktop\Contract.xls not supported . Therefore, the excel file cannot be imported to the SRM system. When I also try to import tablimited format of .txt files, I got same error message and unfortunately I cannot achieve central contracts to be imported. How can I solve this issue? Should I check some customizing settings or something?
Many thanks for your guidence,
Mehmet Gullu

Creating Central Contract using Reference Purchasing Org

Hi,
We are using two type of purchasing organization:
a.Global Purchasing Organization - It is not assigned to any company code or plant.
b.Country Purchasing organization u2013 It is assigned to Global Purchasing Organization. This cross-plant country specific purchasing organization is to procure materials for several plants independent to a company code. We have assigned the purchasing organization to the plant and not to a specific company code.
Global purchasing organization has been setup a reference purchasing organization to be able to create central contracts that is independent of company code and plant.
However whenever we create the central contract using the reference purchasing organization, the system will not proceed unless we define a company code. Please let me know how we can avoid the Pop up message u201CThe Purchasing organization XXXX has not been assigned to a company code. Please enter a company code.u201D
Please note that neither Global nor Country purchasing organization is assigned to company code. The company code will be determined only from Plant.
Please help.
Regards,
AG

Hi.
In your case, both the Purchase organizations ( Global Purchase Organization & Country Purchase Organization ) are not assigned to the company code. But Country Purchase Organization is assigned to the plants from the different company codes and Global Purchase Organization is not assigned to any plant also.
In this case, If you are creating central contract with the Global Purchase Organization , you will get error. Becuase Global Purchase Organization is not assigned to any company code or plant.
If you are creating central contract with the Country Purchase Organization, system will allow. Because this purchase organization is assigned to the plants from the different company codes. Based on this plant, system will identify company code.
So, conclusion is Purchase organization is must be assgined to the plants. This setting is mandatory in order to indentify company code which is giving in the Purchase document. But the assignment of company code to the purchase organization is optional.
So, assign plants to the Global Purchase Organization and try to create central contracts. It will work.
Regards
KRK

Distributing Central Contract from SRM to ECC

Hi,
We are using SRM 7.0 with ECC 6.0 in backend (no EHP). We're setting up a central contract with IDOCs. From what I read we have made the configuration:
in SRM:
- Assign attribute CT_PROC_TY = CCTR
- Connfigure new condition type PB00 which is the same with ECC price for contract
- activate the BADI BBP_DETERMINE_LOGSYS and coding it so for contract it will always go to backend (in method CONTRACT_LOGSYS_DETERMINE)
- I have activated BADI BBP_CTR_BE_CREATE but writing no code, as there no need for me to do mapping
in ECC:
- Activate inbound IDOC type BLAORD and COND_A and assign it to the logical system of SRM
Then I create the contract in SRM. but:
1. When creating contract, in item overview, i cannot tick 'distribution' indicator. Not sure what is the function
2. In item detail, tab distribution, I cannot put create release-purchasing org. Even when using search help it is not giving any value
Actually dont really understand the usefull of the indicator above, so I let it be empty, then I release the contract
The contract then not appear in ECC. I have checked SMQ1/SMQ2 nothing. Even in WE05 in ECC nothing. The only thing I see is in SLG1 where I see error triggered by user WF-BATCH with message "No recipient found"
Do i miss something in here? Any help will be very appreciated.
Josh

Hi Josh,
Central contract is only possible in SRM 7.0 with ECC 6.0 EHP 4. You can use local contracts or GOA.
Regards.

Central Contract Backend document number is not come back

Hi, all~
Pls pay attention this issue.
I saw similiar question but not answered.
We implemented SRM 7.
After Central Contract create, Contract number is transfered to ECC but didn't back.
In tracking tab, there are no backend number.
And I think this is related with XI.
when i check sxmb_moni, 'PurchasingContractSRMReplicationConfirmation_In' message status is not Grand Prix flag.
(Status is 'Transfer to External Applcation', not 'Process Successfully')
What is solution?
Best regards,
SKY.

Hi~ sushil...
Thanks for answer.
I already check /SAPPO/PPO2.
The error message is 'The attributes of the user are inconsistent or not defined. See transaction PPOMA_BBP.'.
But there are no inconsistency or undefined attribute.
We checked it through 'PPOMA_BBP' and 'BBP_CHECK_USERS'.
Could you recommand other way to find out exact point(attribute) about error message?

SRM 7.0 EhP 1 central contracts with service lines

Hi,
I have a question concerning the use of SRM 7.0 EhP1 central contracts with service line items. I know that for SRM EhP 1 you would require EhP 5 in ECC. However, since my organisation just went to EhP 4 last weekend I am wondering if there's any option to use services in central contracts without going to EhP 5 in ECC.
Kind regards,
Bastiaan

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

SRM 7.0 / ERP 6.04: Config. of Central Contract Management

Hello,
I want to configure the newly introduced integrated Procure-to-Pay Scenario Central Contract Management.
I found SAP Note number 1268821 where all tasks are described in order to implement the previous scenario.
For correct implementation, business function "Purchasing - SAP SRM Integration" (LOG_MM_P2PSE_1) activation is required in the ERP Systems.
When I run SFW5 t-code in order to activate the previous business function, SAP system gives an alert message.
What are the consequences of this business function activation ??
Thank you
Michele

Hi Michele,
I don't think there will be any consequences, we had certain warning messages aswell when we activated the business functions in ECC 6. Reading the warning messages we could conclude it wasn't any serious problem.
Details on functionalities included in a business function can be viewed here: [http://help.sap.com/erp2005_ehp_04_sp/helpdata/en/42/fbded750e61febe10000000a422035/frameset.htm] -> Business Functions (SAP Enhancement Package 4 for SAP ERP 6.0) -> Business Functions in SAP ERP -> Logistics -> Materials Management -> Procurement - SRM Integration
Kind regards,
Tim

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

Configurations needed for distributing central contract to backend system

Dear Gurus,
I have configured central contract and getting approved in the local SRM system. Now, I need to distribute the central contract to the backend system. I have already get the PI interfaces configured using the integration scenario Central contract management.
Now, I assign the backend POrg as well as the target values for the backend contract and try to release the central contract. The central contract is getting released. However, no contract is getting created in the backend system.
I donot see any XML messages generated in the SRM system (SXMB_MONI).
Do I need to maintain some settings in the SRM system to enable the distribution of contract to the backend system?
Thansk and regards,
Ranjan

Hi,
When one creates Local Contract; there is one option named 'Distribute' on contract screen.On drop down; one mention back end system. After clicking on it; contract has been created in ECC.
If contract is not getting generated in back end; refer SAP Note: 609222.
Check whether you find any error/information message in Txn BBP_CTR_MON.
SRM Settings:
1. Implement BBP_DETERMINE_LOGSYS: Determines whether contract is to be created in SRM or ECC.
2. Assign transaction type to attribute CT_PROC_TY in Org Structure.
3. Check whether have maintained message type BLAREL, COND_A, BLAORD.
4. Assign role SAP_BBP_STAL_START_PURCHASER to process contracts.
Helpful SAP Notes: 641919, 646903
Regards,
yaniVy
reward if helps

Central contract distribution trough IDOC - including new partner

Hi,
I created a partner in SRM for use with a specific central contract that I am distributing the ECC through an IDOC, the contract in backend is configured with this partner as mandatory, but if I process manually the data in the IDOC in ECC, document is not created, message error is that new partner missing.
Any ideas how can I add a partner in this process?
I'm working with SRM 7.0 and ECC 6.0
Regards,
José Luis D.

To trace where your issue might be, it is helpful to find out the following:
1) in table BBP_BACKEND_DEST, get the SYS_TYPE value for your backend system (LOGSYS = your backend system)
2) in table BBP_FUNCTION_MAP, get the function name for OBJECT = BUS2000113 and METHOD = TransferFromData and TYPE = <your value from step 1>
If you are going through IDOC processing, likely the Function would be "B46B_CTR_TRANSFER". In that case, set a session breakpoint in that function module. Then test run FM BBP_PD_CTR_TRANSFER with your contract GUID as input parameter and IV_SAVE_DB = "X". Execute until the breakpoint and start tracing the problem. This should help you identify the source of the error.

Central Contract -- Sch Agreements error in SRM7 -- ECC6 Eph4

Hello,
While creating a central contract in SRM7 and distribution to BE ECC6 Eph4. I am getting a condition mapping error in the IDOC.
Central contracts to contract in BE uses PI
Central Contracts to Sch Agreement in BE is IDOC.
I see an erro " Errors occured in Mapping operation for conditions data" When i check the FM META_CTR_CHECK .
Mapping conditions are maintained in the ECC
SPRO--> Integration with Other SAP components > Central Contracts> Maintain Conditions.
The same settings work in the development system. I see an entry with 003 Message number in table BBPD_CTR_IDOCREF.
Any help is appreciated. Thanks

Hi Netaji,
I know this has been closed for sometime now, I thought I should tell you that you can send central contract from SRM 7.01 to ECC 6.0 Ehp4 and above using non PI webservices.
Please find the link below just for your information
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi
Regards,
Naveen

SRM 701 - Central Contract via XI, no backend ECC contract created

Hi All,
We are trying to implement the SRM Central Contract Management scenario in SRM701 and ECC 604 using XI/PI and we are finding that the XML message is getting generated OK, passed through XI/PI OK and is successfully processed in ECC, however, no backend contract is created. The SRM number range against the ECC contract document is incrementing every time we send a message but no data is getting committed to the tables. I have seen a few threads on here with others having experienced a similar problem, however, I can't anywhere see what the resolution was.
We are pretty sure all the config is correct as we have tried changing the entry in BBP_BACKEND_DEST for SYS_TYPE to ERP_2.0 and passed the data successfully via RFC and IDOC, but we are not having any success when the SYS_TYPE is ERP_4.0 and using XI.
Please can anyone out there help?!
Thanks a lot...

Hi prashant
I never tried service . but you can see this below symptom for you.I extensively worked on Material contracts.
Are you creating contract from Process contract or Via RFQ
Note 1272305 - Total value wrongly calculated in Contract Service lines
Symptom
We create a Service contract in the R/3 Backend from RFQ. During the transfer we calculate the gross price based on the quantity,price and price unit. (ie) The field ESLL-BRTWR is filled with following formula in the idoc processing. ls_e1edc20-BRTWR
= ( is_item-price * is_item-quantity ) / is_item-price_unit.
AS total value of the service lines is calculated based on the field NETWR which is passed as blank from SRM, during recalculation total value when we change the gross price of one of the service lines in r/3, it is required to fill this field
till PI values are brought correctly till posting to ECC. ?
Note 1123292 - Net Price wrongly calculated in plug-in MAP_BLAORD_SERVICES
my experience in GOA
Note:-
2 set stream of DATA comes from SRM as BLOARD and COND_A ..
Even some times when we reprocess failed IDOCS in BD87 in ECC ( comes contract data from SRM as GOA and failed due to some data validation in ECC). now data issue was fixed at Material master level. and
if we forget to reprocess COND_A - BLOARD creates a successfull GOA but net price shows as ZERO for each material and when you post the COND_A data and correct price will be updated in ECC contract. so kindly check price data reaches or not not or price calculation failed in ECC.
Muthu

Central Contract Header Message

Similar Messages

Maybe you are looking for