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

Similar Messages

Sch Agr with Central Contracts

Hi Gurus,
Need some inputs:
We are implementing classic SRM 7 with BE ECC6 Eph4.
Did anyone work on distributing the central contracts to BE as Sch Agr.
1. Any lessons learned, challenges. etc.
2. Heard there are issues with Multiple line items?
3. Will the scheduling agr release information get updated in the central contracts? Reason for asking this we would like to trigger the central contract alerts.
Any info is appreciated. Thanks

Processing Delivery Schedules
You can use this business process to process delivery schedules. Scheduling agreements are a form of purchase agreement for which the delivery of the total quantity is over a certain time period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates. Scheduling agreements support the following procurement forms:
Standard
Subcontracting
Consignment
Stock transfer
Scheduling agreement releases are issued to the supplier, requesting delivery of the required materials on the dates shown. A creation profile determines which event triggers the creation of a scheduling agreement release, how the delivery dates are displayed (aggregation and release horizon), and whether backlogs and immediate requirements are determined. A tolerance check can be carried out for releases that are created due to changes to the overall delivery schedule in the system.
Scheduling agreement processing is heavily integrated with planning functions. The scheduling agreement releases can result directly from a planning run without requiring further involvement of a purchaser. Before you can use scheduling agreements, you must maintain the source list, including the MRP indicator for relevant items.
Suppliers can issue confirmations (order responses) to the relevant purchasing organization indicating their compliance or noncompliance with the scheduled delivery dates.
You can work with or without release documentation for scheduling agreements.
With release documentation
The schedule lines in the system have internal character and are not transmitted to the supplier until you explicitly create a scheduling agreement release. This may take one of two forms:
Forecast (FRC) delivery schedule
Just-in-time (JIT) delivery schedule
All scheduling agreement releases are stored in the system. Thus you can monitor the scheduling agreement releases, or compare selected scheduling agreement releases with each other.
Without release documentation
The schedule lines are immediately transmitted to the supplier.
Process
The following business process runs in SAP SRM:
Create/process scheduling agreements
Release scheduling agreements
Transmit and monitor scheduling agreements
Process delivery schedules and releases
Transmit and monitor delivery schedules
Administrate scheduling agreements
Monitor/view list display of scheduling agreements
http://help.sap.com/saphelp_srm70/helpdata/en/79/d5962a003a4865b21cf3cdf42cf75b/frameset.htm

Error in migo posting with respect to sch agreement

Hi
I created a purchse requisition and also a sch agreement with respect to it and maintained delivery scheduled.
PR item qty=10
sch delivery=2 4 4 i.e.equal to 10
but when i post GR with respect to this it gives error as follows
PU Ordered quantity exceeded by 2 KG
what can be possible reason.
Thnx

Hi,
Please check the SA - Schedule lines & also the Purchase document history to confirm the total order as well as GR quantity.
Also Please check the Purchase Order unit & Base unit of measure for the material.
Thanks & Regards,

BOM not copied to sch. line in Sub Contract scheduling agreement in Kanban.

Hi,
We are trying to procure material (A) via subcontract scheduling agreement document using Kanban process. This subcontract material has a valid BOM (say it has child materials B & C). We are working with 'Replenishment element for kanban' model (not JIT call).
When Kanban bins status is changed to empty, a schedule line is placed in the subcontract scheduling agreement. But when we try to view the BOM of the schedule line created (Item -> components -> overview), we dont find any child material (B&C) attached to it. Hence when Kanban bin was changed from RED to GREEN, material movement 101 takes place for parent material (A) but 543 (consumption of child materials) is not happening for child materials (B &C).
Mean while, we created some schedule lines manually in aforementioned SC sch.agreement. When we view the BOM of this manually created schedule line, we can see the child materials attached to it. Hence when bin status was changed from RED to GREEN, both 101 & 543 movements were posted.
Can anyone let us know what needs to be done so that when Kanban bin is changed to EMPTY, it places schedule line in SC sch.agreement along with its BOM (Child material) details?
Warm regards,
Saravana.

Dear Ashok,
Issue: how to make BOM field(Component Part) in PO/ SA field non editable in MM customising. After the PO is saved user can not able to edit the component field in PO or Scheduling Agrreement.
BOM field ( component Part ) is directly dependent on quantiyu of material entered. so once you change the PO quantity the component quanity wil change accordingle,
presently you can not achievev thease
but You can set the release strategy like that Po that it is not changable, doing so u r requirement willl achieve
Hope your query is resolved

Error in good receipts for sch.agreement

hi frnds,
while i make gr w.r.t sch.agreement. it is telling that " Document xxxxxxxxx does not contain any items ". i have maintained delivery schedules in day format. and iam trying to do gr in tht date too. but still it is not showing.
how could i resolve..kindly help me..
regards,
prasath

Hi Prasanth,
There have been several reasons which can be attributable to this problem -
1) This PO is subject to release strategy and since the final release was not made, this PO is considered as 'blocked'.
2) You have been using the confirmation control category where in respect of the last confirmation category key, the GR assignment check box is flagged. In this particular case, GR is only be posted if the confirmation is not maintained.
3) Early delivery date i.e. the GR date is coming earlier than the PO delivery date.
Check also the movement type used:should be 101.
Regards,
Nani.

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

Facing problem in creation Central contract in SRM 7.0 System

HI Experts,
We have implemented Classic scenario in P2P business application.
We are facing problem in creation Central contract in SRM system as we using SRM 7.0 .
Error show Application error in back-end system (SAP SRM outline agreement* & Differing time interval
Status show Document complited ->Distribution Incorrect >Created>Complate > Released.
Please Reply
Sharad

Hi Sharad
some mapping error with ECC and SRM
expand the COND /BLOARD . you must get some clue - in bd87 51 error code
did you map pricing condition type with ECC and SRM?
kindly check BADI mapping in SRM
Muthu

Badis for PO and Central Contract in SRM 7.0 in classic

Hi everyone,
I need you help. We are working in a implementation of SRM7.0 with ECC 6.0 Ehp 4 in a classic scenario. We want to know which badis we can use in order to change the purchasing group of the PO an Central Contract when their are transfered to ECC.
BR,
Ivá

Hi Muthu,
We are wondering if it is posible the following:
- An user wants to create PO form SRM. This PO in SRM has the Purchasing group XXX, but (for any reason) we need when this PO is send to ECC, the system changes the purchasing group to YYY.
BR
Ivá

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

Error while installing ECC6

Hi All
i am trying to install ECC6.0 and i face the following error during central instance installation.
ERROR 2007-10-03 11:25:42
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-10-03 11:25:42
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
I did find a solution to this problem on the Internet which tells us to increase the SAG_MAX_SIZE. I did try to set this parameter at the OS level in INIT<SID>.ora from 321807974 to almost double and tripple this size. The thing is i donot know what exactly this size should be set too.
My system config is
RAM - 2Gb, Hard Drive-500Gb in three partiotions(20,120,340).
Virtual Memory- Initial is 2046 final is 4024.
Os- Windows 2003
Jdk version is j2sdk1.4.2_13
Db is Oracle 10g
Could any try and help me out with this error.
Thanks in advance.

Hello Bharani,
This could be any number of problems. First of all you need to consult the logs referenced in the sapisnt log,
import_monitor.java.log
import_monitor.log.
These logs will tell you whihc tabbart is failing, and you then need to check the associated logfile for that tabbart, for example it could be sapappl.log or sapslexc.log.
These logs will provide you with detailed information as to why the tabbart is not loading correctly.
Kind Regards,
David

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.

Benefits of implementing Central Contracts in SRM 7.

Dear Experts,
Picture the following:
- Classic Scenario.
- One ECC 6 EHP 4 Back end.
I'm currently exploring the benefits of implementing Central Contracts against using only Purchasing Contracts in ECC and replicating them to SRM for use in the Shopping Carts.
So my question is why would you implement central contracts in SRM instead of just replicating these contracts from ECC? What benefits would you get out of having central contracts in place against having only Purchasing Contracts in ECC?
Thanks for your input.

adding to Manju one point .
- Procurement department(PURCHASER) can use web interface to create / manage contracts rather GUI interface and quick contract creation / maintenance
- Approval mechanism simplified with less efforts.
- Different ways to create a contract from SRM
Copy an existing contract
Use an existing template
Upload an external file
Upload a contract from the catalog
Muthuraman
1.You can use this business process to access SAP SRM contract features, such as contract hierarchies, discount across contract hierarchies, and grouping logic, when determining source of supply in SAP ERP.
2.You can create a central contract in SAP SRM, and it can then be used as source of supply in both SAP SRM and SAP ERP. Relevant data is sent to SAP ERP for a source of supply determination, and a specific type of contract or scheduling agreement can be created there.
3.While determining a source of supply, you can access central contracts directly.
4.The price is determined in SAP SRM before the SAP ERP purchase order (PO) is sent to the supplier.
5.You can create and change central contracts and renegotiate existing contracts directly with a supplier, or through the creation of an RFx. You can automatically assign a contract as a source of supply, or it can be listed as one of numerous potential source of supply contracts. A strategic purchaser can create a contract whenever they anticipate a long-term relationship with a supplier.
6.Contract management enables purchasers from various parts of the company at different locations to take advantage of the terms of globally-negotiated contracts for specific product categories. You can provide users with specific levels of authorization to contracts, and you can categorize documents as confidential.
6.You can distribute central contracts to release-authorized purchasing organizations, and these organizations can then use them as source of supply in the appropriate SAP ERP system. Hierarchies can be used to organize, structure, display, and search for contracts.
7.If you use SAP NetWeaver Business Intelligence (SAP BI), you can view various consolidated reports of contract management. For example, you can view aggregated value released against all contracts in a contract hierarchy.

Central Contract, MDM Catalog, and classic scenario

Dear SAP experts,
We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
Best regards,
John

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

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

Similar Messages

Maybe you are looking for