Relationship of MA and Contract document

Hi Guys,
     I'm learning how to develop workflow for approving contract. I need to know how the MA and Contract Document work. So when i try to create Contract Document , there is a input to select the MA template. So, when i try to create the MA there is a tab for the Contract Document. I guess that there should be relationship between MA and Contract Document. I want to ask you the following question.
1. Do MA and Contact Document have dependency on each other?
2. When creating Contact Document, is it mandatory to have MA as a parent document?
3. I have seen in example code when developer want to manipulate on Contract Document ex. Save , change phase , add approve, They always get Parent IBean from the Contract Document to do that?
P.S Could you please provide the tutorial link or blog for clearly understanding on MA and Contract Document.
Noppong,
Thank you in advance

Hi,
Here are some answers:
1. Do MA and Contact Document have dependency on each other?
Yes, they are related.
Master Agreement document is the parent( or container) for contract document and they share a associative relationship.  A Master agreement document can have one or more Contract documents associated with it.  In an assoiciative relationship, the lifecycle of documents are decoupled. Which means master agreement and contract document lifecycles are decoupled, meaning a contract doucment can be edited by one user and a master agreement can be edited by another user at the same time. 
2. When creating Contact Document, is it mandatory to have MA as a parent document?
Yes. contract document cannot stand alone
3. I have seen in example code when developer want to manipulate on Contract Document ex. Save , change phase , add approve, They always get Parent IBean from the Contract Document to do that?
Because of the relationship, contract document refers to the collaborators in the master agreement/agreement . Contract document supports workflow, where as the master agreement document doesn't.
Thanks, Baski

Similar Messages

  • Separate document no. for SD revision document and detagging relationship between invoice and SD document no.

    HI,
    Country specific settings for India - Business transactions enables SD revision vide table TE872_SDCTRL_IND.
    Whenever SD revision takes place system issue similar document no. as that of invoice and tagged it with XBLNR as per standard process.
    Now issue that if that invoice is reversed, subsequent SD also gets reversed.
    So business requires to have separate document no. for SD revision document and detagged relationship between invoice and SD document no.
    I have explored event R507, 0010, 0060 and R436 but couldn't find input structure where such separate document can be assigned.
    So can you provide hint which can assist in issue resolution?
    Regards,
    Paresh

    Check this thread, if this helps.
    [url] Link between MKPF table and EKKO or RBKP table [url]
    I've done this as well earlier to create a custom document flow for archived documents where from the EBELN i've found all the related documents. Hope this helps.

  • Relationship between invoice and billing document in 3rd party

    Hi Experts,
       Is there any relationship between vendor sending invoice to us and we send billing document to customer in third party scenario ? If yes, kindly let me know the relation please.
    Regards,
    Prasath

    Hi Adwait,
       Thanks for your reply.If the 3rd party vendor sends invoice for quantity 50  to us and the3rd party vendor has delivered the quantity 30 to customer. Which one is to be done first?   invoice from vendor or billing document to customer? How do i check how much the 3rd party vendor has delivered to customer ?
    Regards,
    Prasath

  • BOM Routing - CA02 - Material,Operation Number and PRT Documents - relationship

    Hi Experts,
    Need some info related to BOM Routing - CA02
    I am trying to update multiple -  Document , Document Type , Document Part ,Document version - for a operation in CA02 .
    All i need to know is how find the relationship between Material and PRT - Document details.
    In which table i can find the linkage?
    Please share your views.
    Cheers!!!
    Karthik Rali

    Hi
    In my opinion, the behaviour is correct....
    If you maintained the BOM for FG 1 Qty - Requiring 1 Qty of each component - Then what system did is correct
    You should have maintained 1 Qty for Comp 1 and 0.9 of Component 2
    Note that, the Qty of Components that you maintain in the BOM relates to the Header Material... and not to the Other Components in the BOM
    br, Ajay M

  • Question about base and target document

    Dear All,
    Does anyone know which table maintain the relationship between base and target document.
    For instance, user clicks the base document in the form of AR invoice and return the base sales order.
    From Samson

    Hi,
    In each and every document table the base docs and the target docs information is stored.
    Just take a look at the REF DB help file in which u can see the fields and their relations.
    For AR Invoice in the lines table INV1 there are 3 fields BaseRef,BaseType,BaseEntry these fields help u in knowing the base doc details, and for the target doc details the following fileds will help, TargetType,TrgetEntry.
    U can find the reference file at the following location. C:\Program Files\SAP\SAP Business One SDK\Help\REFDB.chm
    Vasu Natari.

  • Different amount in Contract and Billing document.

    Hi All,
    We have a issue here, need suggestion.
    We have a contract which has a billing plan. We have maintained monthly plans with a fixed amount.
    Say we have $ 1000 in the contract, but the billing has been created with $ 900.
    So you see the amounts are different in contract and billing document.
    We have checked there are no recent pricing changes or any such changes that will have such effect. The invoice is created in May.
    There were pricing changes in March but they had been corrected in March itself.
    Let me know if anybody has faced such issue and where may be the issue.
    Regards,
    SB
    Edited by: Satish Bharambe on Jun 2, 2011 11:43 PM

    You would have to cross-check the Pricing at Item level in Contract & Invoice. Hope , it would help you to check the Base Price or some other Prices / Discounts.
    Best Regards,
    Ankur

  • Contract ID and Purchase Document No in MM

    Guys,
    Please help me to understand if contract ID  and Purchase Document No in MM
    will be the same thing or not.. In a report i need to get Purchase Document No but
    in the datasource i have only contract id.. To my knowledge contract is a document type under purchasing...So contract id should be equal to the purchase document no in that case... is it right???? Please confirm

    Hi,
    well both numbers are stored in the same field. In your source system it is ekko-ebeln. But the document type defines the number to be a purchase order or a contract no. And so it is in BW. The number is stored in the same infoobject, but together with the document type you can identify that number as a purchase order or a contract no.
    Hope that helps!
    kind regards
    Siggi

  • PABR01 and PABR02 in contract documents configuration

    Hi,
    I was tryong to find out the use of the fields PricProcCondHeader and PricProcCondItem in contract document.  Please let me know the following:
    1)  What is the usage of the fields PricProcCondHeader and PricProcCondItem in contract documents?
    2)  When do we use these fields?
    3)  What is the difference in pricing procedure at header level and pricing procedure at item level as pricing is always for the items.  Then why do we need the pricing procedure at header level.
    4)  How do we use the pricing procedures PABR01 and PABR02 that are available for these fields.?
    Please answer the above questions and through some light on these fields.
    Thanks
    jayant

    Hi All,
    Please advice on the query posted above.  Please let me know when are the fields PABR01 and PABR02 used.  Please throw some light.
    Thanks

  • Consignment  sale and contract difference

    What is the basic difference between consignment sale and contract ?
    Thank u gurus

    Consignment Sales is a sale, in which initial ownership of the stock is with us, the stock being in the premises of the customer. The ownership is transfered on sale of material.
    Contract may be quantity contract or Value contract, in which the stock remain in our owm premises, but it ia an agreement to delivery some'x' quantity of material or materials to the tune of decided valuue.
    <b>Consignment Stock Processing:</b>
    Consignment Stock Processing
    Purpose
    Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
    Consignment Fill-Up:  Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
    Create a sales order using order type KB.
    Enter the required data on the customer, the consignment goods and the delivering plant.
    Enter all other relevant data and save the order.
    Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
    The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
    Order type: KB (document category C: sales order)
    Std. Delivery type: LF
    Item category: KBN (not relevant for pricing and billing)
    Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
    Copy control rules for the sales doc, item category, and schedule line category.
    Use trans MB58 or MMBE to check the stock.
    Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
    Create a sales order using order type KE.
    Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
    Enter all other relevant data and save the order.
    Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
    The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
    Invoice the delivery which issues the consignment goods.
    Order type: KE (document category C: sales order)
    Std. Delivery type: LF
    Invoice: F2
    Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
    Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
    Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
    Create a sales order using sales order type CR.
    Enter the required data on the customer and the consignment goods.
    Enter all other relevant data and save the order.
    Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
    Create a credit memo for the consignment return you created in Step 1.
    Order type: KR (document category H: returns)
    Delivery type: LR
    Credit for Returns Order type: RE (delivery or order related billing)
    Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
    Schedule line category: D0 (relevant for deliveries, no availability check, 634
    Consignment Pick-Up:  The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
    It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
    Create a sales order using order type KA.
    Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
    Enter all other relevant data and save the order.
    Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
    Order type: KA (document category C: sales order)
    Delivery type: LR
    No invoice
    Item category: KAN
    Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customer’s consignment, 632 (Consignment pickup)
    <b>Contracts</b>
    Contracts represent special business relationships with customers based upon material, price, and qty. They guarantee a special price agreement with the customer and are usually called outline agreements in std SAP terminology.
    There are four different types of contracts provided by SAP. They are:
    1)     Quantity contracts
    2)     Value contracts
    3)     Service and maintenance contracts
    4)     Master contracts
    Regards,
    Rajesh Banka

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • Exit for role determination via exit for scheduling agreement and contract?

    Hi..
    I have a requirement to fetch the agents in run-time for PO,PR,SCHEDULE AGREEMENT, CONTRACT..
    For PO i am using EXIT : - M06E0005
    For PR release i am using EXIT :- M06B0001
    By using above 2 exits i am getting the agents at run-time...
    Same way i need the EXIT for SCHEDULE AGREEMENT and CONTRACT..
    if there is any EXIT for this please share with me..
    Regards,
    Imtiaz Khan

    Hi Imtiaz,
    Ideally you should have your agent determination logic in workflow itself instead of determinining them in EXIT.
    Can you tell me why you are determining agents in exit and how you are making use of it ?
    Also let us know how your workflows are getting trigger for all these documents.
    Regards,
    Ibrahim

  • Creation of Purchase requisition with reference to Contract documents

    Dear All
    I am not able to create the Purchase requisition with reference to Contract documents, in outline agreement field if I enter the contract document number which is already existing it is not copying the details, again I have to enter all the details like Plant, Material, document type, Qty etc.  Even after selecting the PR document type as RV for outline agreement also it is not coping. Kindly let me know that can we not able to give reference of Contract number in this outline agreement field to create Purchase requisition.
    regards
    Dhanu

    1.Logistics--Materials Management--Purchasing ---Purchase Requisition --Follow-on functions --- Assign and Process
    2.ME57
    3.Select the Assigned Purchase Requisitions checkbox if you also want to see requisitions already assigned, and choose Execute.
    4.On the Assign and Process Purchase Requisitions screen, select the requisition lines for your material.
    5.Choose Assign Manually if the info record already exists.
    6.On the pop-up Assign Source of Supply Manually dialog box, make the following entries:
    Agreement     46XXXXX            Agmt item     10          
    7.Choose Assign Source of Supply.
    For assign the source of supply, you can also choose Assign Automatically (only if not already assigned by MRP due to existing source list). If more than one source exists, select the contract in the Source Overview for Purchase Requisition 100XXXXX window and confirm with Enter.
    When assigning a source, make sure to select the contract.
    8.Choose Save.
    9.Select the line item, and then choose Assignments Overview (SHIFT+F5).
    10.On the Assign and Process Requisitions: Overview of Assignments screen, select the line below Vendor (you can only select one at a time), then choose Process Assignment.
    11.On the Process Assignment: Create PO window, check and make sure the Order Type (NB), Purchasing Group and Purch. Organization fields then choose Continue (Enter) to confirm.
    12.On the Create Purchase Order screen, select the requisition in the Document Overview section and choose Adopt in the left part of the Document Overview screen.
    13.Choose Save.

  • Read-only Collaborator can edit Contract Document properties

    We have a master agreement with a read-only collaborator. The security profile for this collaborator role is identical to the stock "Document Reviewer" profile, i.e. only View is set.
    However this supposedly read-only collaborator is able to edit Contract Document properties. They click on the Contract Documents tab, then drill into a Contract Document, and then click on the Edit button. From there, they have the ability to change fields such as Name, Descrpition, Effective Date, etc. They cannot change or delete the actual file attachment itself.
    Is this an issue with CLM, or is there some security setting we are missing somewhere? Please tell me this is not working as designed ..
    thanks.

    Hi Terry,
    According to your description, my understanding is that you don’t want the yollow bar notification to display when you open Access documents.
    This issue seems to be about the client application. Please compare the followings with the things that you did:
     1.Open the documents
     2.Click File->Options->Trust Center->Trust Center Settings
     3.Click Protected View, unselect ‘Enable Protected View for originating from the Internet’
     4.Click Message Bar, select ‘Never show information about blocked content’
     5.Click Macro Settings, select ‘Disable all macros without notification’
    In addition, as this issue is about Office, I commend you create a new thread in Office forum, more experts will assist you with this issue.
    Office forum:
    http://social.technet.microsoft.com/Forums/en-US/home?category=officeitpro
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Not able to attach final signed document in the contract document

    Dear Experts,
    The upload field for final signed document in the contract document is visible only for the latest/last contract document if there are more than one contract document exist in the Master Agreement.
    For the previous contract documents, not able to attach final signed document (i.e) the upload field is invisible.This scenario is occuring only in few master agreements, mostly found in Legacy agreement types.But for newly created legacy agreements this scenario is not occuring.Please help me in finding out why the upload field is visible only for the last/latest and not for the previous ones.

    Hi Dinesh,
    Did you find a solution to this?
    Regards,
    NR

  • Vendors Unable to Check-In Contract Documents (e-Sourcing 5.1 Patch 06)

    Vendors Unable to Check-In Contract Documents (e-Sourcing 5.1 Patch 06)
    When moving to patch 06 for e-Sourcing we found that Vendors were no longer able to check-in contract documents, even though they checked them out successfully.
    On Patch 05 this was not an issue with the exact same configuration.
    Has anyone had any encounters with this? 
    - Is there a permission that needs to be set to something specific?   I tried create/read/edit but that doesn't seem to work.
    Thanks.

    When working with a Master Agreement or Sub Agreement within e-Sourcing you can attach Contract Documents (Word files) that you and the vendor can collaboratively work on. 
    Just like a source control system you can check out a document to make edits to ensure that no one else makes edits at the same time.  You then must check back in the document to remove the 'lock'. 
    On patch level 06 we found that although Vendors could perform the Check-out procedure (On a Contract Document click Actions -> Check-Out) they are not permitted to then check-in the document (Actions -> Check-In).
    Buyside users do not experience any issues with check-out/in.
    Hope that helps clear up the issue.
    Thanks,
    Greg

Maybe you are looking for