Creating release order from contract

Hello
I tried to create a relase order from contract. But it gave me the message
"Partner XXXX is not authorized to release from the contract"
In the customization of the contract type WK1 I have maintained the setting as A for the field check partner authorization.

HI,
Pl find solution on
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fdbb545a11d1a7020000e829fd11/content.htm
Vrajesh

Similar Messages

Creating sales order from contract ISA R/3 Edition

Hi Forum,
Our scenario are
1 - customer select product from catalog and place order from internet
2 - sometimes, customer already have a contract with us (created earlier manually on SAP) and want to create sales order from internet referencing a SAP-contract.
For scenario No.1 - we can use standard SAP
For scenario No.2 - is there any standard way to do so? or we have to do customization?
Any suggestion are welcome.
Thanks a million.!!

Hello
"Contract Processing" is not supported out-of-the-box in ISA R/3 edition.
However, you have a good news. The OSS Note [788245 |https://service.sap.com/sap/support/notes/788245]- "ISA R/3 4.0: contract processing", explains how to implement this feature on a project basis.
We have implemented this feature successfully at few customers.
Hope this helps.
Easwar
http://www.parxlns.com

Create PO(release order) from contract

Hi,
   I have created a contract using me31k with one item,then I creted a relese order PO with same item.when I enter another item in my relase order PO which is not there in the my contract,here system allow me to add item and save without any problem.Why system does not stop this? If it is standard behaviour,then how to prevent ?.
For this issue,can some body throw some light on this issue,please?
With Regards,
Jaheer

Hi,
   The release order means the PO item created with reference to the contract item. There can be multiple items in the PO in which some items can be with reference to contract - these items eventually becomes the release orders and other items can be without reference to contract.
   In short, you can add multiple items in PO where some items can be with reference to contract item and some are not. This is standard behavior.
Regards,
AKPT

Release orders from quotations

Hi Experts,
i trying to create release orders from quotations, but im unable to find the field which contains release orders in the popup which appears when we create with reference.
Note : I am able to create release orders from contacts.
thanks.
Raghu

U create an order with reference to Quot. and release orders for contracts.
Cheers!!!
Anupam

Release orders against contract 4600000069 not possible (contract not relea

Hai,
I had created a contract and had a release procedure for it.
I had released the contract using ME35k.
When i try to raise a p.o agaist the contract i am getting the error as "Release orders against contract 4600000069 not possible (contract not released)"
What could be the problem and solution for the above error message.
Thanks
Hari.

Bijay Kumar Barik wrote:
Hi,
>
> Error clearly says, contract not released. Release order can be created against contract ,if contract is released.Check=> you may used ME35K to release the contract , but after releasing with releases code, you have not saved the release .Just do use again ME35K to release the contract with release code & save.
>
> NOTE:
> Also check how many levels of release is there for contract and check all levels of release with respective release codes is done or not before creating release order WRT contract.
>
> Regards,
> Biju K
I had released and saved for all the levels i.e for all the release codes.
Still it is behaving the same.
I have not used any ref purchase org as mentioned above in one of replies.

Creating Sales Orders from Quantity Contract - ORDERS05 IDOC

Hi,
I have created a Quantity Contract in ECC. Now I want sales orders to be created w.r.t to the Contract through ORDERS05.
Can anyone suggest which IDOC Segment and Qualf i have to populate to achive the same.
Also say once I am able to achive the creation of Release Orders from the Contract through ORDERS05. If I surpass the Qty of the Contract . The IDOC should be have a field for notifying the same.
REgards,
BInayak

Hello Binayak
You may use the following segment and fields for reference data:
Segment: E2EDK02
Fields:
QUALF : IDOC qualifier reference document - I think for contracts this is '001'.
BELNR : IDOC document number
POSNR : Item number
As per a flag to indicate that the contract quantity is surpassed, I doubt there will be anything like that becasue is an Idoc is before you created the order and how will the system know you have surpassed until an order is entered?
I think you need to use 'completion rule' and copy control 'update document flow' features to work on this.
Hope this helps.

How to create release order for value contract?

dear experters,
I create a value contract by T-code:va41, order type"WK1".I set a Assortment module to this order and mateirl "WKM1" to it.
then I create release order by T-code:va01 with refrence to this value contract,but it set the material "WKM1" to the sales order, and I can't modify this material! I want to put another material which belong to the assortment module in the value contract. I want to know how.
thanks.
Best regards
lance

Assortment Module for Value Contracts
This function enables you to define a list of materials that can be released from a value contract. Materials can be assigned to more than one assortment module.
An assortment module is an entry tool and can be called up from the value contract. It is valid for a certain time period.
If you delete a material from the assortment module, to which a value contract refers, you will be unable to release that material.
In the value contract, only materials with the same sales organization and distribution channel as the value contract can be taken from the assortment module. All the other materials in the assortment module are not displayed in the value contract.
To fulfill both these requirements, two types of value contracts are offered in the standard system:
Value contract type WK 1
You can specify a product hierarchy or a assortment module for value contracts with contract type WK 1. The system will always propose this type of contract, if you want to create a contract for several materials or a certain group of materials. All the materials in the relevant assortment, or belonging to the specified product hierarchy are then relevant for release.
Value contract type WK 2 (material-related)
You can create contracts for one material (usually configurable) with this type of value contract. A software company is an example of where this kind of contract is often used. There, a contract for the value of $500,000 is made with the customer for one specific software product.
You can also agree on the length of the contract for this type. The contract duration can be agreed at item level and can be different from the contract duration specified at header level.
You can store special price agreements for the value contract. These price agreements can then be used at any level. For example, a value contract can contain prices for individual materials, or discounts that are valid for every released material.
Release Orders
The customer fulfills a contract by issuing orders against the contract. The contract does not contain any exact dates for deliveries, so you need to create a sales order to release against a value contract.
When a release order is created for the contract, the system automatically updates the released values in the contract. The release order value is calculated from the total of the open order and delivery values, plus the value that has already been billed to the value contract.
The system also updates the released value for subsequent changes (for example, overdelivery of contract release, price changes in the billing document, partial deliveries, returns, rejection of order items, cancellation or reversal of orders, deliveries or billing documents).
You can create a release order in any currency. The system automatically converts this currency into the one agreed upon in the value contract on the pricing date for the contract release order.
Creating Assortment Modules for Value Contracts
Procedure
To create an assortment module, proceed as follows:
1. From the initial screen choose Logistics >Sales and Distribution >Master data.
2.Choose Products >Value contract - Assortment module > Create.
You will then be in the Create assortment module: Initial Screen.
Module type 6 is defined for the value contract.
3. For external number assignment, enter a module number.
You can then use existing modules as a reference by entering the name of the module under reference.
4. Choose Enter.
5. Enter a short description for the module.
6. Enter a validity period for the product proposal.
During a release, the system checks if the release date lies within the validity period.
7. Create the materials that you wish to assign as items to a module.
You can display a list of materials as a product proposal, which you can then copy into the assortment module. To do this, choose Suggest material, enter the selection criteria in the subsequent screen and copy the selected materials to the items. Use Edit > Delete item to delete the materials that you do not want to copy to the assortment module.
8.Save your entries.
Also Please check the copy control in VTAA
Regards,
Anbu

Error while posting a sales order created with reference from contract for

Hi,
I am posting a sales document( Type: WA) created with reference from contract document( type wk2) for delivery. The item category in the sales order of the Item is WAN. On posting this document for delivery I am getting the error as "Item category WAN is not defined". Please help me out how to resolve this issue.
Thanks
Jayant

Hi Jayant,
I think its value contract releated error,
You suppose to check material item category group through T.code-MM02 into sales2 tab and maintain VCIT,
and do item category assignment through T.code- VOV4.
plz.maintain like that,
WK2 -          -VCIT-         -           - WAN(contract item category),
wk2 -          -        -VCTR-          - WAN((contract item category),
you should also maintain same against your standard Sales Document type and for Standard Item category into VOV4,
WA(standard docu.type) -VCIT-                             -                -TAN(your standard docu.type item category),
WA(standard docu.type) -         -VCTR(item usage)-              -TAN(your standard docu.type item category),

BADI trigered in CRM while creating a order from B2B webshop

Hellow Gurus,
Could you please tell the BADIs triggered in CRM when we create an order from B2B webshop. I have to keep a validation to ensure the delivery type 'Standard' should be applicables orders having gross weight less thatn 4 kg only.
I should also throw an alert in B2B webshop saying ' Please choose other type' as well. I dont know how to proceed for this.
Please help.

Hello,
The best way to determine the BADI's called is to look at the Log files. The following OSS Notes (based on your release) will instruct you how to create a session trace.
Note 569976 (Release 4.0) - creation fo session logs
Note 1090753 (Release 5.0) - Creation of logs for B2B and B2C
Note 1156730 - Creation of logs for ISAUserAdm and ShopAdmin
You can also look at the [Modifiation and Extension guide |https://websmp210.sap-ag.de/~sapdownload/011000358700000469462006E/]for instructions (chapter Session Tracing).
I hope this helps.
Deb

Update was terminated while creating purchase order from ME21N

Hi Experts,
We are getting this dump when try to create purchase order from ME21N;
Our system ECC 6.0 and IS-AFS (Apparel & Footwear Solution) V600 component has installed,
How can we prevent this error,
Regards
Here is the dump and sm21 log,
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Exception              CX_SY_PROGRAM_NOT_FOUND
Date and Time          10.10.2008 10:22:03
Short text
     Program "RMCMS431 " not found.
What happened?
     There are several possibilities:
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCS4" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     or
     Error in the SAP kernel.
     The current ABAP "SAPLMCS4" program had to be terminated because the
     ABAP processor detected an internal system error.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
     caught in
    procedure "TMC2F_FROUT_CALL" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RMCMS431 ".
    However, program "RMCMS431 " does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
How to correct the error
    Check the last transports to the R/3 System.
    Are changes currently being made to the program "SAPLMCS4"?
    Has the correct program been entered in table TSTC for Transaction "ME21N "?
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
    "SAPLMCS4" or "LMCS4F10"
    "TMC2F_FROUT_CALL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "TMC2F_FROUT_CALL" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
sm21 log ;
Transaction Canceled 00 671 ( LOAD_PROGRAM_NOT_FOUND 20081010102203saptest_TET_00 EYUCE 100
Update terminated
> Update key: F39796DD5421F1509233001E0BD601E0
> Update module: MCE_STATISTICS_UPD_V2
Run-time error "LOAD_PROGRAM_NOT_FOUND" occurred

Please follow the oss note 800335
V2 Update terminations in Purchasing transactions after upgrading or installing AFS 5.0 release.
Other terms
AFS, LIS, MIGO, ME22N, OLI3, S433, S431
Reason and Prerequisites
AFS Purchasing infostructure S431 is no longer used. S433 is the valid infostructure for the release AFS 5.0.
Solution
Please do the following.
For customers upgrading to AFS 5.0 only:
> Rebuild Infostructure S433.
- Goto transaction: OLI3 (Statistical Set up of Infostructures)
- Info structure to be compile: S433
- Specify the 'Name of run'.
- Execute.
> Please also follow the instructions given below.
For both Upgrade and Non-upgrade Customers:
> Create the report 'ZDELS431'.
- Transaction: SE38
- Give Program name as ZDELS431.
- Create (F5).
- Title : 'Program to delete S431'.
- Type : 1 (Executable Program).
- Status: T (Test Program).
> Copy the program text from the note and paste in the program.
> Save and activate the program.
> Execute the report for all clients in Update mode.
(Two check-boxes will appear: P_ALL_CL, P_UPDATE.
   Please check both of them).
This report will delete all the references to infostructure S431.

Release orders for contracts

Dear Gurus,
When we create release orders with reference a quantity contract, PO quantity can be more than the contract quantity. How to limit the quantity of the PO to less than the quantity in the contract?
Thanks,
Chameendri

Dear Chammendri,
Now the message number is 042 and application area is 06.
Go to SPRO -> materials management -> Purchasing -> Environment data -> Define attributes of system messages à system messages.
On going to the system messages we get this screen
For this particular message type we find u2018Wu2019 which means a warning message is issues by the system.
To change this message type to Error message type, we change the u2018Wu2019 to u2018Eu2019.
Regards,
PK.

Creating Release orders

Hello Experts,
I read that when creating release orders, "assign an order item to a contract retrospectively."
Can you clarify what is meant by that? why retrospectively?
Does it mean:
1. can add an order item to a contract after a contract created?
or
2. assign a order item to a contract by way of release orders?
or
3. ?
Thanks.
M Russo
Edited by: Mirella Russo on Jan 11, 2011 6:17 AM

Dear Russo
Retrospective , generally means to take a look back at events that already have taken place.
Create a Release Order, wrt a contract.
Only for items relavnant to the contract.
Rgds
Sumanth.G
Consultant/Systems Analyst- SAP SD/MM

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Serial number copy functionality when creating return orders from standards

Hi all,
Serial number is not copying when i create return order from the standard orders in below scenario.
I implemented one BADI for copying Serial number to Sales order when doing Post goods receipt.
So after doing inbound delivery and PGR, serial number is copied to the sales order but when i create return order with reference to the Standard order Serial number is not copying.
When i go VA02 for standard order and selecting the technical objects then if i create the return order serial number is copying.
Please help me in the above issue.
I used the following logic to copy serial number from inbound delivery PGR.
UPDATING THE SERIAL NUMBER TO THE RESPECTINVE SALES ORDER LINE ITEMS
            CALL FUNCTION 'SERNR_ADD_TO_AU'
              EXPORTING
                sernr                 = lwa_sernr-sernr
                profile               = 'NEOP'
                material              = lwa_mseg-matnr
                quantity              = 1
                document              = lwa_mseg-kdauf
                item                  = lwa_mseg-kdpos
                debitor               = lwa_mseg-kunnr
                vbtyp                 = 'C'
                sd_auart              = lv_auart
                sd_postyp             = lv_pstyv
              EXCEPTIONS
                konfigurations_error = 1
                serialnumber_errors   = 2
                serialnumber_warnings = 3
                OTHERS                = 4.
            IF sy-subrc = 0.
              CALL FUNCTION 'SERIAL_LISTE_POST_AU'.
            IF sy-subrc EQ 0.
              COMMIT WORK.
              WAIT UP TO 2 SECONDS.
            ENDIF.
Edited by: Rajesh Sanapala on Feb 16, 2009 12:48 PM

hi.
I have the same problem.
Can you please share how you solved it?
thank you
Bill

Create Sales order from Internal Purchase Order using IDOC

Hello Friends,
I have requirement to create Sales Order from Internal Purchase Order Using IDOC.
Backgorund, we have already configured IDOC orders05 to create Sales Order from external Purchase order from Inbound IDOC, and it is working fine.
Now we have new requirement to create Sales Order from our own Purchase order, i.e. When PO is created in one plant corresponidng sales order automatically must needs to create in another Plant with respect PO.
I m trying to design a solution for above problem as follows,
1.create an Inbound Idoc from PO, by creatiing one new message type on PO save.
2.Process that Inbound IDOC same as it is from external PO.
3.Once processed Sales order will create.
Please help me in step 1. to create Inbound IDOC from PO.
If you want any further clarification please write me.
Thanks,
Mahesh

I had done a similar scenario before and we achieved it through SAP XI. The problem is with the control record. When we create a ORDERS IDOC from a PO the control record will be for outbound transmission. We sent the file to XI and XI resent it back with some data parsing and a new inbound control record. This way it went neat outbound and inbound.
I'm not sure what kind of architecture you have. If you have to do it within your ECC/R/3, then you could create the outbound IDOC to a new port and write a fresh RFC to pick it up from the same folder and create a new control record for inbound processing.
I haven't tried this; but there is a "processing w. trigger (inbound)" option on the outbound process code. May be you can explore into that a bit more.
I'm sure there could be better approaches to handle this within ECC so if you stumble on any, do write back. I would like to know to update my knowledge .

Creating release order from contract

Similar Messages

Maybe you are looking for