Prerequisites for transaction COHV to close settled orders automately

Dear friends,
     What are prerequisites for transaction COHV to close settled orders automately?
     I really want to know these prerequisites because I came accross a problem: After finacial dept. settles production orders, it is usually for them to close production orders by using Transction COHV. But, Last month, They closed several orders that should be closed this month by using COHV.
     Preliminary reason: I found that these orders' variances were 0 and the stutus was DLV because these orders are produced completely at beginning of this month. And,  the time to close orders after settled is behind these activities. So, I have a question before. Is there any settings to restrict the period? I think restrict to the period can solve this problem.
best regards

Close the question. thanks.

Similar Messages

  • BAPI for transaction IW31 (creating a work order)

    Hi all,
    I need to be able to create a work order ( IW31) using ABAP code and was wondering if any knew if there was a BAPI that should be used for this functionality.
    Thanks in advance
    Mart

    hi,
    You can use
    BAPI_ALM_ORDER_MAINTAIN.
    Have a look at the following documentation.
    FU BAPI_ALM_ORDER_MAINTAIN
    Text
    Process Maintenance-/Service Order
    Functionality
    This Business Application Programming Interface (BAPI) is used for changing maintenance- or service orders and their lower-level objects. The following objects of an order can be processed (for restrictions, see the note at the end of the documentation):
    Order header
    Partner
    User status
    Order operations
    Relationships
    Components
    Long texts for order header, operations, and components
    Function
    Calling up this BAPI once allows you to perform all the operations. For this the system supplies the function module with a method table containing the methods to be performed. The entries in the method table refer to data records in the optionally filled-out data tables. All the methods from the method table are performed. Alternatively, just lower- level objects from existing orders can be changed.
    You can process the transferred data with the Business Add-In (BAdI) IBAPI_ALM_ORD_MODIFY to, for example, merge data from the external system with data from the R/3 system. The BAdI is called up as soon as the transferred data is converted into the internal format. The tests then take place after this.
    Construction of Method Table
    REFNUMBER Reference number for linking object methods - attributes
    The reference number is the line of the database which contains the corresponding data. The data table is determined by the object type.
    OBJECTTYPE Object category
    The object category specifies which object from the order should be processed. The key words listed here are not language-dependent and must be transferred exactly as they are. The following objects exist:
    HEADER Order header
    PARTNER Partner data
    USERSTATUS User status
    OPERATION Operation data
    RELATION Relationships
    COMPONENT Components
    TEXT Long texts
    (empty) ,General BAPI functions (save)
    METHOD Methods
    The methods with which the data should be processed. The following functions exist:
    CREATE Create objects
    CHANGE Change objects
    DELETE Delete objects
    RELEASE Release
    TECHNICALCOMPLETE Technically complete
    ATPCHECK Availability check
    CALCULATE Calculate
    SCHEDULE Schedule
    DELELTEDSEX Delete the status for external scheduling at operation level
    SAVE Save all data
    DIALOG Call-up dialog. See explanation below.
    TRACE Write trace file in the specified file to the frontend
    OBJECTKEY SAP external object key
    This key is for assigning the lower-level objects correctly to the corresponding objects, as there is always just one key in the data table. The key must have the following structure:
    1-12 Order number
    When creating orders with internal number assignment, a reference number beginning with % must be entered here. The BAPI then returns this number and the number actually assigned.
    13-16 Operation number
    17-20 Sub-operation number
    For relationships, the key is structured as follows:
    1-12 ,Order number from
    13-16 Operation number from
    17-28 Order number to
    29-32 Operation number to
    The following methods are permissible for the individual objects:
    HEADER:
    CREATE, CHANGE, RELEASE, TECHNICALCOMPLETE, ATPCHECK, CALCUALTE, SCHEDULE
    OPERATION
    CREATE, CHANGE, DELETE, DELETEDSEX
    PARTNER, RELATION, COMPONENT, USERSTATUS, TEXT:
    CREATE, CHANGE, DELETE
    (empty):
    SAVE, DIALOG, TRACE
    Data tables and update tables
    The objects have one or more data tables. For some objects you can specify which of the fields specified in the structure should be changed. For this you must set the field in the corresponding table to X as in the data table. If no update-table is transferred, then only those fields are set that have a value that is not initial. This simplifies the transfer data. However, this means it is not possible to delete fields. If an update structure should only be specified for some data records, the table with the update fields must nonetheless have the same amount of lines as the data table. The empty lines are then treated as if no update structure was transferred. The objects "Partner", "User Status", and "Text" have no update tables. The whole data record is always copied here.
    References
    The objects use the field REFNUMBER from the method table to refer to the lines in the data table. Counting always begins with 1. In doing this, REFNUMBER also refers to the update table. However, in the method table there is a second reference to higher-level objects for lower-levels objects. The field OBJECTKEY must be filled with order number, operation number, and sub-operation number, as specified above. If lower-level objects of a newly-created order should be changed, then you must enter a temporary order number that must begin with %. Several orders can be numbered serially, for example, with %00000000001, %00000000002 ... .
    The following objects have special treatment for REFNUMBER:
    Partner
    Texts
    Partners have an order number in the data table. During processing of the method table, all those entries in the data table are processed which have an order number that is the same as that in the line to which the method refers. Thus, through just one entry in the method table, several partners can be changed.
    Texts are composed of two tables. The first table (IT_TEXT) is made up of the header data of the text. Here you must specify the object and the first and last line of the text table (respectively inclusive, counting from 1). Through this, a line segment is specified in the text line table (IT_TEXT_LINES).
    Peculiarities in processing
    The BAPI processes the transferred methods in a particular sequence, which must not correspond to the sequence in the methods table.
    Write trace file
    Change user status time period 1
    Delete objects (dependent first)
    Create new objects
    Change existing or newly-created objects
    Change user status time period 2
    Status change of order
    Save data
    The methods are performed such that lower-level objects can also be assigned to newly-created objects. For example, first the operations are created, and then the components. Long texts can also be created for the objects.
    Components have an exceptional position. Components are created through the assignment to an operation, that is, using the "key" order/ operation (item number). However, as this is not the unique component key, you can only access the components to change them, delete them, or add long texts by using the reservation number/-item, which is only given after saving. This means that, for example, you cannot create a long text when you create the component.
    User status changes can take place at two different time points. Time point 1 is before the object changes, time point 2 is after the object changes and before the status change of the system. These time points should be defined in the transfer table in the field CHANGE_EVENT. The field documentation contains the possible values.
    The external scheduling is offered by the BAPI as a special function. THe BAPI can set the date field directly at the operation level, and select the operation with the status DSEX "Date set by external system". This status prevents any further scheduling of the operation, it keeps the transferred dates. For this, set the category 'X' in the restriction categories. When reading the operation, this category is also returned, independent of the category of restriction set in the dialog. To delete the status, you can call up the method DELETEDSEX for the object operation. The external scheduling cannot be influenced in the dialog. All changes to the scheduling restrictions in the dialog are saved as normal, but are not relevant for the scheduling as long as the status DSEX is active.
    Every time the BAPI is called up, a SAVE or DIALOG method must be transferred. Normally, calling up a BAPI is seen as a transaction. All data that is changed in the BAPI should be saved to the database immediately. The BAPI checks whether a SAVE method exists, otherwise it terminates processing. A test run of the BAPI is composed of a normal call-up using the SAVE method and a subsequent BAPI_TRANSACTION_ROLLBACK. To call up the BAPI without the SAVE method, for example, to realize dialog transactions, the BAPI can be called up with the DIALOG method. This switches off the check for the SAVE method. The processor must then ensure that later either a SAVE method or a BAPI_TRANSACTION_ROLLBACK is called up.
    A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing in the update to ensure that no inconsistent data is written to the database. The processor who called up the BAPI does not receive any confirmation for the termination of the update in the target system. This logic is necessary as the order data was flagged for updating with BAPI_TRANSACTION_COMMIT through the SAVE method. However, the status information was already flagged for updating when the BAPI was called up. A BAPI_TRANSACTION_COMMIT without SAVE method then just saves the status information and would generate inconsistent orders, if the updating was not terminated.
    Customer Enhancement
    The BAdI IBAPI_ALM_ORD_MODIFY can be used to change the transferred data. The BAdI is called up after the conversion of the transfer structure into the structures used internally. Additional data can be transferred using the table EXTENSION_IN. Only then is the data checked.
    Example
    The following examples should clarify the use.
    Creating an order
    OBJECTKEY should be filled with a temporary key. The BAPI returns this key together with the assigned order number in the return table ET_NUMBERS . The order number in the HEADER table should also be filled with the number. For external number assignment, the external number should be specified. The update structure can be transferred if necessary.
    Methods table
    REFNUMBER OBJECTTYPE METHOD OBJECTKEY
    1 HEADER CREATE %00000000001
    IT_HEADER
    ORDERID ORDER_TYPE PLANPLANT ...
    %00000000001 PM01 1000 ...
    Creating an order with operation and long text
    Methods table
    REFNUMBER OBJECTTYPE METHOD OBJECTKEY
    1 HEADER CREATE %00000000001
    1 OPERATION CREATE %00000000001
    1 TEXT CREATE %000000000010010
    IT_HEADER
    ORDERID ORDER_TYPE PLANPLANT ...
    %00000000001 PM01 1000 ...
    IT_OPERATION
    ACTIVITY SUB_ACTIVITY CONTROL_KEY WRK_CNTR ...
    10 PM01 MECHANIC ...
    IT_TEXT
    ACTIVITY ... TEXTSTART TEXTEND
    10 ... 1 2
    IT_TEXT_LINES
    TDFORMAT TDLINE
    Longtext for operation 10, line 1
    Line 2 of the long text
    Notes
    Using the BAPI to process the order data cannot support all the functions of the transaction. This applies in particular for the following functions:
    Order header data
    The object list cannot be processed.
    Refurbishment orders are not supported.
    The estimated costs cannot be processed - only the estimated overall costs of the order.
    Notification data cannot be processed with the order BAPI. Even if the settings in Customizing are such that the orders and notifications can be maintained on one screen, no notification is created for the order.
    Permits cannot be processed.
    The order addresses cannot be processed.
    Individual partner addresses cannot be maintained.
    The settlement rule cannot be maintained.
    Order functions
    Printing the papers is not possible.
    Locking and unlocking the order is not possible.
    Accepting and rejecting quotations is not possible.
    Business completion is not possible.
    Flagging for deletion is not possible.
    The log cannot be displayed.
    User default values are not used.
    The field selection is not checked.
    The Customer Exits/BAdIs are not executed completely.
    Joint ventures are not supported.
    Funds Management is not supported.
    Investment orders are not supported.
    No integration of service products with task lists possible.
    No integration of configurable service products possible.
    Assignment of sales document items with service products in accordance with the aforementioned conditions.
    Operation data
    A change of the control key in the operation is not possible, if this leads to a change of the processing type (internal-/external processing)
    User status change not possible.
    Production resources and tools cannot be processed.
    Service lines cannot be processed.
    Task list integration is not supported.
    Linking operations with object list is not supported.
    Component data
    User status change not possible.
    BOM data cannot be processed.
    The delivery address cannot be processed.
    Further Information
    See also the documentation for the individual transfer tables.
    Parameters
    IT_METHODS
    IT_HEADER
    IT_HEADER_UP
    IT_HEADER_SRV
    IT_HEADER_SRV_UP
    IT_USERSTATUS
    IT_PARTNER
    IT_PARTNER_UP
    IT_OPERATION
    IT_OPERATION_UP
    IT_RELATION
    IT_RELATION_UP
    IT_COMPONENT
    IT_COMPONENT_UP
    IT_TEXT
    IT_TEXT_LINES
    EXTENSION_IN
    RETURN
    ET_NUMBERS
    Exceptions
    Function Group
    IBAPI_ALM_ORDER
    ~~Guduri

  • Switch off availibilty check in transaction COHV

    Hi All,
    I want to Switch off availibilty check in transaction COHV while converting planned order tp production order.
    Can any one know procedure?
    Thanks,

    Hi,
    Yes you can block availability control checking from OPJK tcode.
    In OPJK you will find 2 business function one is availability check in creation time and second  one is for release time..
    Select go to detail in material availability tab there are option u can activate and deactivate availability control
    Arun

  • Line item Settlement and KOB5 for automatically created AUCs to PM orders

    Hello Experts,
    I am trying to set up line item settlement for automatically created AUCs. We would like to use line item settlement because we want to see the costs split up by either percentage or amount when settled to the AUC.  If I can't settle by percentage or amount to the AUC then i'd like to be able to temporarily block some of the costs from settling.  This is for billing not capitalization purposes since all costs will eventually settle to one final asset. The settlement is done using transaction KO88 or KO8G and automatic processing type.  I’ve configured a PM Order type as an investment order and set up the related investment profile and investment asset class.  Some of the things I've determined from my testing:
    Using transaction KOB5, costs can be split up by creating other distribution rules, but only to another object (i.e. another
    asset, order, cost center etc. by using the Preliminary) not to the automatically created AUC linked to the order
    The default settlement rule is account assignment category FXA, percentage rate 100%, settlement type AUC to the AUC
    and therefore cannot be updated/altered when using KOB5 or any other transaction.
    Once the costs are settled to another object other than the AUC, those costs cannot be settled to the final asset. Creating Preliminary
    settlement rules to a receiver IO and changing the period or fiscal year will not “block” costs from settling whether the processing type is automatic, by period, partial capitalization or full settlement.
    I’ve been testing this out in our development client and need verification that this is the way that transaction KOB5 works with line item settlement or did I do something incorrect . 
    Your feedback is greatly appreciated.  Thank you in advance.

    Hi Zaid,
    Thank you for your response.  Assets are not my area so I’m not sure if I missed a transaction or step in the process.   I tested this out by doing the following steps:
    Created AUC Asset class with line item checked
    Assigned PM Order type as non-investment with no investment profile and created order number
    Created a main asset number 
    Created an AUC sub asset number to step 3
    Created settlement rule to sub asset number on order
    Posted costs to order
    Settled from order to AUC with transaction KO88
    Created distribution rules for asset with transaction AIAB
    Settled from sub asset to main asset number with transaction AIBU
    When I settled from the sub to the main asset number in step 9, I found I lost the line item detail.  Is there another configuration setting I need to make to allow me to see the line item detail when I use AIBU?
    Thank you,

  • Prerequisites for archiving the sales order

    Hi ,
    What are the prerequisites for archiving a sales order? What is the last business transaction from which the archiving process is triggered? Is it necessary to set status CLSD on the sales order for archiving ? what are the other system statuses that should be set for archiving a sales order?
    Thanks & Regards
    San

    Hi Santosh,
    Sales Order is linked to other subsequent documents in the Order Processing cycle like Delivery, Invoice , Shipments, etc. So, we've to make sure that all the dependencies are removed before we can start to archive an SO.
    You can see the dependencies in SARA Transaction (Goto->Network Graphic).
    The SO archiving program checks if the status of the subsequent documents are Completed or not. (status in VBUK table is "C") .
    There are other options like Residence Time, Existence of PO , Existing of Accouting Doc.
    You can select the options, based on your company's decision regarding the extent of SO archiving they wanted to achieve.
    The program will throw the messages appropriately, based on the checks it performed and appropriate actions can be taken from the document side .
    This is a link , which explains the checks the program does before archiving.
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/a9/55c7d490a111d1a5510000e82deaaa/content.htm
    Regards,
    Shail.

  • Transaction code to view process orders set for deletion

    Hi PP Gurus
    We are trying to search for transaction code to view the process orders which have status as DLFL i.e deletion flag  set for the orders. In cooispi, the deleted orders are not shown in the report output.
    I request you to let me know if there is any other code through which we can view deleted process orders.
    Thanks & Regards
    Harleen Kaur

    Dear,
    In COOISPI  put DLT in system status field and execute the report this will give you the list of all order with deletion flags
    Also refer this thread,
    COOIS Report for Production orders with status DLFL
    Regards,
    R.Brahmankar
    Edited by: R Brahmankar on May 6, 2009 11:16 AM

  • Table for transaction code for creation of process order

    Hi Gurus,
    Please tell me, in which table i can see the transaction code used to create process order.
    regards
    Kaisar

    Hi,
    Table for transactions is TSTC.
    If your looking for t-code for process order - COR1.
    Regards,
    Vivek

  • PREREQUISITE FOR PURCHASE ORDER MASS MAINTENENCE

    Dear Experts,
    Please explain the prerequisite points for the purchase order Mass Maintenance.
    i want to set Delivery completed indicator for the open purchase orders.
    is it prerequisite for setting the deletion flag to the purchase order items.
    if delivered quantity is more the PO order quantity, it is not allowing to set the deletion flag
    also it issues the warning message of release PO - Release already affected.
    Please explain the concept in brief.
    Thanks in Advance

    Hi,
    When you set the "delivery completed" indicator, it considers a purchase order item to be closed. This means that no more goods receipts are expected for this item. If the "delivery completed" indicator is set, the open purchase order quantity becomes zero, even if the full quantity has not been delivered. It is still possible to post goods receipts for the remaining quantities.
    When you set the "delivery completed" indicator:
    The purchase order item is considered closed, even though the total quantity may not have been delivered.
    Although a further delivery is not expected, it is still possible.
    At the time of the next goods receipt, the system suggests the item as unselected in the item selection list.
    The purchase order item can be deleted, even if the total quantity was not delivered..
    Thanks and Regards,
    Maheshwari

  • ALE Configuration for Transactional Data (Purchase Order)

    Dear Experts,
    I want to configure ALE for Purchase Orders(Transactional Data).
    For that:
    I have done neccessary Condition  Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
    Now I have 2 queries.
    i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
    ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
    Regards
    Arnab

    Hi kumar,
    what Alexander  said is absolutely correct .
    from your second question no master data distribution configuration is required for the transactional data distribution.  
    let us know once if you face any problems.
    ~linagnna

  • List of orders for which varience calculated and settled

    Dear Friends,
            How to list out the production orders for which variance calculated and settled by each period wise,Please give me a solution.

    Hi,
    U can find some status of order in COOIS T code or in Order it self.
    Go to COOIS
    Select the option in status field.
    SETT - Order Settled,
    SETC - Settlement Rule Created
    SETM - Settlement rule created manually.
    TECO - Techo  (Once order is Completed).
    without techo order is not settled.
    Regards,
    Pavan PP

  • User-exit for transaction co13: PP Order Cancel Confirmation

    Hello!
    Whether prompt, please,
    exist what that user-exit for transaction co13: PP Order Cancel Confirmation?
    Thanks,
    Anton.

    Hi Antonio,
    Please check this all user exits (SMOD) available for CO13.
    CONFPP01  -  PP order conf.: Determine customer specific default values 
    CONFPP02  -  PP order conf.: Customer specific input checks 1           
    CONFPP03  -  PP order conf.: Cust. specific check after op. selection   
    CONFPP04  -  PP order conf.: Customer specific input checks 2           
    CONFPP05  -  PP order conf.: Customer specific enhancements when saving 
    CONFPP06  -  PP Order Confirmations: Actual Data Transfer               
    CONFPP07  -  Single Screen Entry: Inclusion of User-Defined Subscreens  
    CONFPS01  -  PS confirmation: Determine customer specific default values
    CONFPS02  -  PS confirmation: Customer specific input checks 1          
    CONFPS03  -  PS confirmation: Customer specific check after op. selection
    CONFPS04  -  PS confirmation: Customer specific input checks 2          
    CONFPS05  -  PS confirmation: Customer specific enhancements when saving
    CONF0001   -  Enhancements in order confirmation                         
    CONFPI01   -   Process order conf.: Calculate cust.specific default values
    CONFPI02   -   Process order confirmation: Customer spec. input checks 1  
    CONFPI03   -   Process order conf.: Cust. spec. check after op. selection 
    CONFPI04   -   Process order conf.: Customer specific input checks 2      
    CONFPI05   -   Process order conf.: Cust. spec. enhancements when saving  
    CONFPI06   -   Process order confirmation: Actual data transfer           
    CONFPM01  -  PM/SM order conf.: Determine cust. specific default values 
    CONFPM02  -  PM/SM order confirmation: Customer specific input checks 1 
    CONFPM03  -  PM/SM order conf.: Cust. spec. check after op. selection   
    CONFPM04  -  PM/SM order conf.: Customer specific input check 2         
    CONFPM05  -  PM/SM order conf.: Cust. specific enhancements when saving 
    Regards,
    Ferry Lianto

  • Any Userexit & BADI for transaction VB(7 during final settlement

    Hi SAP GURUS,
    I have checked no user exit and BADI. Any Userexit & BADI for transaction VB(7 during final settlement. During final settlement of rebate, I have to change the amount from KONP table in transaction VB(7 . Let me know the userexit and BADI.
    Regards,
    Karthik.

    Hi Sekhar,
    These following BADI are not capturing KONP item details.
    I want to capture KONP item details to modify amount.
    ARC_SD_COND_CHECK : Archiving Object SD_COND: Additional Checks
    ARC_SD_COND_WRITE : Archiving Object SD_COND: Archive Additional Data
    SD_COND_SAVE_A : Save condition application A, E
    Regards,
    Karthik.

  • The Prerequisites for releasing process order

    Hi all,
    What are the Prerequisites for releasing process order?
    Can we issue the material against process order, if it is on CRTD status?

    Hi,
    Prerequiste for REL of Process Order -
    Process order should have CRTD status.
    Other with IMG setting, you can have order status directly REL once it is created also. See Prod Sch Profile setting.
    You cannot do goods posting (GI and GR) unless order is REL status. Not possible with CRTD status.
    Srini

  • Actual settlement: Orders !! help

    Hello to everyone, first at all thanx.
    when i am using the transaction "K08G" Actual settlement: Orders, and i recover the settlement period ( period 9 ) , fiscal year 2009 and execute it ....
    Appear a quantity " 12.207u20AC " and it is wrong cos  In G/L account Line item display, there are four  line/ items and i can clear it 2 to 2 .
    I hope the system read something wrong cos ... it four line / item have got  a value date 09.2009 then in Actual settlement: Orders must be appear NILL " 0 " .
    For that i need change or repair december 2008 and september 2009. Cos it items have got a  document date ( 28.09.2009 and 31.12.2008 ).
    How can i repair it ????  the year 2008 is close!! any idea???
    thank you very much

    dear Dave
    thanks for your advise, we can not change the current filed customizing.
    I am not able to understand why , even if in the Maintain Allocation Structures we have defined a specific Settlement Cost Elements (for exp 600019) during the actual settlement (TCODE KO8G) for some order the system doesn't respect the allocation structure definition.
    some one can help me?
    regards
    marco

  • Standard tcode for (mass) data change of internal orders or ... ??

    Hi!
    I really need some info if there by any chance SAP has standard transaction for mass data change of internal orders (more particular, distribution rules in settlement rule section, which can be found in <b>KO02 transaction</b>  ).
    I am trying to change distribution rules for settlement receivers in <b>settlement rule section</b>, that is finish past distribution rules by filling TO PERIOD and TO FISCAL YEAR fields on the right of each rule, and then entering new rules (which i get from external source -flat file, ms excel, csv...).
    If i wanted to import data in SAP i guess i would have to develop a Batch Input. But that would take me some time to develop because it is pretty complicated.
    I found tcode KO08 but i do not really know how to use it. Maybe there is another tcode that i am not aware of?
    I would appreciate any suggestions!
    Thnx, UK

    Hi Srilakshimi,
    If you are familiar with MASS transaction, then you can modify User Responsible field for Internal Orders from transaction KOK2.
    As first step you must create a selection variant in order to define which orders you want to modify. Once selection variant was created, excute transaction with it and you'll get a screen similar to MASS transaction. Select the field you want and massively replace it. Do not forget to save.
    Best Regards!
    Mgitur

Maybe you are looking for