PO reffering ECC contract

Hi
When I try to create a PO referring an info record as a source ,it creates the same(PO) but when a ECC contract is referred as a source,it does not create PO.
When we check error it suggests some internal error.
Can any one suggest the possible reason for this failure
Thanks in advance
arjman

Hi Arjman
you can see Inforecord as a SOS as like contract in the SC.
if your Inforecord is valid . date/org data and it must populate for sos.
inforecord is also one of the main source of supply in classic scenario
check any development mad in SRM not to show inforecord as SOS.
or create one iforecord for one material and create a sc for that material. you must see in the sos folder of sc.
br
muthu

Similar Messages

  • Tax Code from ECC Contract or Info Record not picking in SRM7.0 SC

    Hi Experts,
    We are configuring SRM7.0 with ECC6 (Ehp4) having Classic Scenario.
    In SRM Tax setting, we set as u201CTax calculation in backend systemu201D, we created and mapped Tax code with ECC and it is working fine.
    In our case, Tax Rate varies as per Mat. Code & Country, irrelevant to Supplier.
    Tax code will be maintained in the ECC Contract /Info Record & we are going to use it as a SoS.
    However, while creating Shopping Cart, we must have to assign the Tax code at item level. If users makes any mistake and enter the different tax code, system does not validate it and create the classic PO with this tax code, which is different than maintained in ECC Contract /Info Record, which will be totally wrong and will create mess !
    In tax code Config setting, we have option to default the Tax code, but it is on Country and Product Category basis  .
    Can someone confirm /suggest me , whether anyhow  can we pull the Tax code from the selected SoS i.e. ECC Contract /Info Record, by using some BADi?
    Thanks
    NAP

    Hi Experts ,
    Any news on this please ?
    Regards
    NAP

  • 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

  • Upload ECC Contracts to SRM

    Hi Experts ,
    Can anyone please confirm me, exactly in which situation , we upload ECC Contracts to SRM..by report BBP_CONTRACT_INITIAL_UPLOAD ?
    We are deploying Classic scenario with ECC6 (EHP4) with SRM7.0.
    Thank you in advance.
    Regards
    NAP

    Initial Upload of Central Contracts and Scheduling Agreements from SAP ERP to SAP SRM. This is just help aid report
    You can use program BBP_CONTRACT_INITIAL_UPLOAD to upload contracts and scheduling agreements from an SAP ERP system to an SAP SRM system. Depending on the settings you make, contracts and scheduling agreements are then uploaded from the SAP ERP system to the SAP SRM system as a central contract. Generally, this initial upload is a one-time activity performed at the time of installation in the SAP SRM back-end system. For more information, see the program documentation.
    Situation could be Some backend contracts wanted to use in Extended classic scenario . so Manual effort is reduced to create a Local contract. so that SAP gave option to reutilise the contract rather than creating from scratch.
    After you transfer a contract from backend to SRM , you must make them inactive other wise this contract will be active at both systems.
    now SAP recently developed some migration reports to convert GOA into CCTR .
    If you are upgrading from an earlier release of SRM / support package of ERP and you are already using SRM Globals Outline Agreements (GOAs) as source of supply in ERP you need to convert the replicated GOAs in ERP to replicated Central Contracts. Please refer to the program documentation of report MMBSI_CONTRACT_MIGRATION. For converting the GOAs created the lower releases in SRM to Central Contract in SRM 7.0 system please use the report /SAPSRM/MIGRATE_GOA_TO_CC. These reports have to be executed saperately in both the systems. The preferred sequence would be to run the migration report in SRM first to convert GOA to CC and then run the migration report in ERP. Running the report in ERP presupposes that the system connectivity regardings SOA services between ERP and SRM has been set up completely.

  • OA vendor changes in ECC COntract from GOA

    I have created a GOA 35000003 with one vendor 11111 (VN) and released and reached ECC as Purchase Contract.
    and
    now i could view in me33k contract header -> partner details as OA 11112 and VN as 11111 o.k
    now next day vendor master team changed OA 11113 FROM OA 11112  for VN 11111.
    Now i create a SC11000012  and PO 70000003 created  for VN 11111 with OA 11112  rather than OA 11113 SINCE MY CONTRACT HAS STILL OA AS 11112.
    Any one faced this problem?
    As per business PO must created with OA 11113 rather than OA 11112 since they have changed in vendor master data.
    i could change in purchase contract but that is not good practice. ..
    as you all aware as a Business process, we are not supposed to change the purchasing contract at any cost. our changes always must be done in SRM GOA. WHAT  TO DO?
    Has any one faced this issue?
    SG :- plz try this.You can suggest any backend method (no 2 method .no problem) but without touching me32k i want to achiece .already autobos (one of our sdner )advised me do via idoc . but give more insights.take your time.hope you understand my problem. you can ask questions if you need any query on this.
    classic:- OA as well as VN both are available in SRM pulled from ECC.(both are same number range)
    now
    MY VN 11111 vendor told us that no more OA 11112 . so we set deletion flag this OA vendor 11112. (OA - 11112 ORDERING ADDRESS NO MORE LIKE ABONDONED)
    vendor may instruct us to set up OA 11113 for VN 11111 and go on.
    NOW i touch xk02 VN 11111 as OA 11113
    now i may need to touch in contract right?

    Hi SG
    there are two vendors in two different states so i do have OA and VN relationship.( really names are same but different address vendors). in one state the vendor may get tax exemption.
    so maintain VN 11111 ABC LIMITED lnc , FLORIDA and OA 11112 ABC Limited ,DALAS.
    NOW i scraped the operation in DALAS , i started new address vendor company in NEWYORK 11113 OA.
    so now VN 11111 ABC LIMITED lnc , FLORIDA  and OA as 11113 ABC Limited , NEWYORK.
    I set deletion flag for 11112 and removed form VN 11111 and new data is IN XK03.
    VN 11111 and OA 11113 .
    SO i need to change the same in contract to other wise my contract always pointing to OA 11112 ABC Limited .DALAS into OA 11113 ABC Limited NEWYORK.
    yes. i do have a OA in SRM side too.
    i dont have separate number range for OA and VN.
    rule:- The contract still pointing to old OA only.contract has VN as well as OA too.
    in SRM , while creating a GOA , i use only VN as my vendor.
    since i am in classic, GOA is not my source of supply. purchasing contract only my sos.
    I need to know the trick to change the OA without touching ME32K.
    PS:- i leanrt and confirmed  from SAP MM experts if i change OA vendor for VN vendor in Vendor master , we need to manualy change the contract  partner details too...
    IN THE MEAN TIME I HAVE SET DELETION TO TO MY OA VENDOR 11112 DALAS TOO
    I also tried to change some piece of data in GOA like some text added and approved and the same contract. no changes on partner data VIA WEB.
    You can ask if you have any questins
    BLOARD
    e1edka1 lf
    e1edka1 ez
    WRF02K- GPARN /GPARVW attack? THROW SOME LIGHT
    SAP suggest 11111 in BP create ONE MORE ADDRESS OA like NEWYORK as OA and Standard address  as FLORIDA  and select the the NEWYORK address and distribute the GOA again. but business did not agree..due to some tax and etc.
    I tried all the possible ways.
    Muthu

  • Total release values in GOA and ECC contract

    Hi  All
    Contract  query
    i just want to match both ECC and GOA release values .
    What is the table Total  release value stored in SRM and ECC other than EKAB (Item release table)
    i want total release value in both system so that i can compare very easily.
    appreciate your help.
    br
    muthu

    In SRM, the total release value is at header level in table BBP_PDHGP / VAL_PO_E. However, we have experienced occasional situation where this value on header differs from the sum on each item (BBP_PDIGP / VAL_PO_E). SAP wasn't able to offer more explanation than recommending that we write an custom report to synchronize them manually.

  • ECC Contract Hierarchy

    Hi,
    How best can we use Contract Hierarchy in ECC 6.0 ?
    Has anybody mapped this process?
    Please share your inputs.
    Thanks in advance.
    Regards,
    Anil Rajpal

    dear Anil
    we can Map contract hierachy in ecc6.0 there is not much diffrance in previous version and new version of sap for contract herachy , we have upgraded our system from 4.7 to 6.0 , and have seen the mapping ...
    for example 
    1.) Distributed Contracts :
    In the SAP system of the "Metal Corporation" in Pittsburgh, a contract for 10,000 tons of "steel 1" is created without specification of a plant under the agreement type "VK" (distributed contracts).
    The company has a plant in Minneapolis, another one in Atlanta, and a subsidiary, "Southern Metal Co.", in Houston. The latter represents a separate company code. The Metal Corporation is the central system, the Minneapolis plant is local system no. 1, the Atlanta plant is local system no. 2, and the subsidiary (Southern Steel) is local system no. 3
    The central SAP system makes the contract available to the local systems, that is to say, it distributes it to enable the latter to procure material "steel 1" by issuing contract release orders. The contract is transmitted to the local systems by means of an intermediate document (IDoc) via ALE, and is imported into each individual system.
    The Minneapolis plant (local system 1), issues a release order for 2,000 tons of steel 1 against the contract. After this, the quantity that can still be released against the contract is 8,000 tons.
    This information must be passed on to the central system. For this purpose, an IDoc is transmitted to the central system, causing the release order documentation there to be updated. At the same time, the release order documentation is updated in the local system that issued the release order (quantity released: 2,000 tons).
    The Atlanta plant creates the next contract release order for 1,000 tons. As a result, the release order documentation is updated both centrally (quantity released according to Pittsburgh documentation: 3,000 tons) and locally (quantity released according to Atlanta documentation: 1,000 tons).
    The release order documentation in the local systems is limited to the relevant entity's own release orders. Only in the central system is data on all release orders consolidated in collective release order documentation.
    This means that the central system has control over the degree of fulfillment of the contract.
    As soon as the complete quantity has been released against the contract, the blocking indicator is set in the central system, thus preventing the creation of any further release orders.
    The subsidiary (which represents a separate company code) can issue release orders against the central contract in the same way as the plants, provided that it uses its own purchasing organization with the appropriate company code assignment in doing so.
    2.) Centrally Agreed Contract
    It is possible to create contracts that do not relate to just one particular receiving plant. In this case, a centrally agreed contract is created without specification of a plant. The plant is not specified until a contract release order is created.
    You can maintain different conditions for individual plants in the central contract or different ordering addresses or goods suppliers in the vendor master record, for example.
    An enterprise with a central purchasing department (= Reference Purchasing Organization) buying materials for several plants can agree a high-level contract which may apply to a vendor's entire corporate group and which can be utilized by other purchasing organizations within the enterprise. The use of such centrally agreed contracts usually results in more favorable conditions of purchase. (Outside SAP, such contracts may also be referred to as "national", "group", or "corporate" contracts.)
    A centrally agreed contract is involved if:
    A single purchasing organization procures for an entire corporate group, or
    A reference purchasing organization makes a contract available to other associated purchasing organizations, enabling the latter to issue release orders against this contract
    for example
    Vendors may assume different roles (partner roles) in the procurement process. Partner roles (sometimes also referred to as "partner functions") include the roles of "ordering address", "goods supplier", and "invoicing party".
    The partners you can store in the vendor master record in the Partner Roles view apply to a certain purchasing organization.
    In addition to the partners that are valid at purchasing organization level, you can maintain different partners for individual plants or vendor sub-ranges. In this case, the system will determine a different ordering address in a purchase order for your Atlanta plant than the one determined in a purchase order for your Minneapolis plant, for example.
    Two individual vendors belonging to the vendor corporate group X supply receiving plants in different regions. In the vendor master record, the receiving plants have been assigned as follows: vendor X2 supplies plant 0001 only, and vendor X3 plant 0002 only.
    If a buyer wishes to release material 4711 against the centrally agreed contract with vendor corporate group X, he or she enters the key for the plant for which the material is to be procured.
    If he or she enters plant 0001, the system determines vendor X2 as the ordering address on the basis of the assignment in the vendor master record.
    If he or she enters plant 0002, the system determines vendor X2 as the ordering address on the basis of the assignment in the vendor master record.
    You can also assign several partners with the same role to a plant (e.g. two ordering addresses). When you create the release order, you are then asked to decide on one of them.
    reward points if helpful
    thanks and regards
    ravikant dewangan

  • Passing custom field in contract in SRM to contract in ECC

    Hi,
    We are using SRM 7.0 with ECC 6 (no EHP). We're planning to use central contract distributed with IDOCs. Our contract in ECC has custom field added in the header. We have tried and successfully pass the contract from SRM to ECC (using IDOC BLAORD03 and COND_A).
    I know we can create custom field in contract in SRM, but how to pass the value in the custom field in SRM contract to custom field in ECC contract? Do we need to edit IDOC BLAORD03? Is it possible?
    Best regards,
    Yosea

    Hi,
    Does anyone know the answer?
    John

  • Net price zero for SRM service central contract in SAP ECC

    Hi
    Net price in backend ECC is showing as zero for SRM service central contrracts, all other price fieids are fine expect net prices. We have no issues for material contract.
    Does any one had similar issue of net price zero? I have tested this scenrio in couple of SRM 7 landscpape all are with similar behaviour. Is it standard?
    Your response is highly appreciated.
    Regard
    Prashanth K Saralaya

    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

  • How can I transfer contract in SRM to ECC?

    Hi Experts,
    How can I transfer contract in SRm to ECC, and then we can do subsequent process, such as PO reference contract.
    Thanks a lot!!!!!!

    Hi Jock,
    Are you trying to transfer local SRM  contract to ECC system?.
    GOA can distribute to backend system as a process contracts and scheduling agreement right?
    local process contract only for SRM system right ? you can not push local contract  to backend .
    However  you can bring backend  ECC contract to SRM .
    what is your business requirement ? which version are you working on?
    since SRM2007 purhase contracts and GOA 's are merged to form a single central contract which is available for sourcing localy in srm and can also be distributed to different backend ECC systems.
    br
    muthu

  • PO replicated in ECC doesn't contain contract number

    Hi All,
    I'm using the Extended Classic Scenario; in the PO automatically replicated in ECC there isn't the contract number.
    In SRM and in ECC I have the same contracts with the same numbers. Then if the ECC PO doesn't contain the contract number, only the SRM contract is used and the release value of the ECC contract isn't updated.
    What can I do to import the reference to the contract number in the PO replicated from SRM in ECC?
    Thanks in advance.
    Best Regards.
    Antonio.

    Hi Antonio,
    i am getting advantage of having contracts in two places, in ext-classical, the contract call-off takes place locally(SRM) and when PO created, it just replicated back to R/3. the contract reference is not pushed back.
    However for reference purpose if you want to do , use the PO business add-ins, but this will require custom development.
    Cheers, Renga

  • CONTRACT mass maintenance in ECC.

    Hello All
    I do have some issues.
    We do Have SRM and create a Global Outline agreements and distribute to backend system as Purchasing contracts.
    DUe to some technical snag Purchasing group name posted in ECC contract.
    Now I need to do quicklyupdate 300 contracts Purchase group name only.
    How we can do by mass update transactions.
    For example :-
    ECC
    contract number :- 23000000
    Purchase Group name :- CAB - CHENNAI
    Purchase Organisation :- 1000
    SRM
    contract number :- 23000000
    Purchase Group name :- MAB - MUMBAI
    Purchase Organisation :- 1000
    i NEED TO CHANGE MASSIVELY MAB purchasing group in ecc purchasing contract  as MAB instead of CAB
    MEMASSCONTRACT. - Helps? have any one tried the same?
    Thanks
    Muthu

    HI,
    Check on it;-
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/408104b5-8ad2-2c10-8383-9b07a2727c4e?quicklink=index&overridelayout=true
    pherasath

  • Question on Contract - Partner function

    Hi all
    For eg.
    I created a CONTRACT in ECC and its vendor as VN 11111 ( OA ORDERING ADDRES  22222.)
    Later Vendor master team changes in the vendor OA as 33333 from OA  22222 for VN 11111.
    Can I expect the same changes in ME33K , HEADER , partner -> porg -> OA as 33333 or OA as 22222?
    can i see the vendor master data changes in ECC contract.
    that means when i create a PO w.r.t my contract , This PO should pick as OA 33333 but it picks ordering as old OA 22222?
    is it right fuctionality?
    appreciate your quick help.
    BR
    Muthu

    Thanks Arun
    Old one needs to be manually corrected. And transactional data takes precedence over the master data.
    Old one needs to be manually corrected - where plese be specific. in the bendor master or contract.
    my question is if i change in vendor master OA , i am expecting contract also must pic the same but it is not happening.
    can you refhrase the answer.
    should i change the partner function via contract -hetail-partner details?
    what does mean only one needs to be manually corrected IN VENDOR MASTER OR CONTRACT?
    Muhtu

  • Contract Creation in SRM 7.0 classic scenario

    Hi All,
    We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
    Question is  -
    1)  Can we  create  contracts in SRM 7.0 Classic scenario ?
    2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
    3) How  we can  transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
    What are the mandatory fields required to transfer the CLM contracts contracts to ECC  outline agreement -  I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
    Rgds/Pawan

    Hi Pawan,
    Please find the answered for your questions:
    Question is -
    1) Can we create contracts in SRM 7.0 Classic scenario ?
    Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
    2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
    Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
    3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
    +Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
    +As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
    +This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
    +Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
    Hope this helps.
    Regards,
    Mitesh

  • SRM and Inventory with a Contract

    Using ECC 6, SRM 7(Extended Classic)
    Contracts maintained in backend and replicated into SRM.
    Inventory Contract created in a 'bulk' fashion - e.g. - without a specific Material.
    Contract is setup in ECC with an Item Category of 'M' (Material Unknown) and an Account Assignment Category of blank.
    If using ECC we then raise a Purchase Order - this works fine.
    When replicating the Contract into SRM it fails error is 'BL001' - Item type error.
    General Scenario - We have a contract for numerous goods (Clothing) , so we enter one (1) line in the Contract. We can't define a specific material on the Contract as the goods required vary ecah Shoppnig Cart - e.g. - Shirt Blue Size 10 on 1 SC, then next day may be Trousers Grey Long - whatever. All of the various types of clothing are covered under one (1) Contract.
    We can;t specify a particular Material on the Contract because the SC (and subsequent PO) will validate against the Contract Material. This all works fine in SRM and it seems that our problem is the inability to replicate teh contract into SRM since it does not recognise the 'M' Item Type category.
    Any guidance appreciated.
    Thanks.
    Gerry Steer

    Hello Gerry
    I dont know the answer but i am telling the fact of SRM
    SRM has three Item types
    Material
    Product category
    Services
    but i understand you use this report BBP_CONTRACT_INITIAL_UPLOAD program to transfer all ECC contract to SRM as a repository upon your business rule,
    SAP SRM dont have idea how material unknown M item category mapped in SRM
    as of i know there is no option in SRM for this MATERIAL UNKNOWN item type .
    SERVICE - AVAILABLE IN SRM
    MATERIAL - KNOWN MATERIAL AVAILABLE IN SRM
    MATERIAL GROUP - Available in SRM
    Please kindly report to SAP via OSS message  , i think this unknown material mapping must be done as equivalent to ECC or some alternative like product category contract.
    Muthuraman

Maybe you are looking for