IW45 - Cancel Confirmation - Posting period query

Hi Experts,
I am executing IW45 and while saving it says that Cancellation of completion confirmation STOPPED due to MM period closed .
As per my knowledge Time confirmation generates only financial document so why it is giving an error because of MM periods?
Also, I want to cancel the confirmation that is been done few days back but the probelm is now that period is closed.
So what are the different ways to go ahead with the cancellation of this confirmation?
Can we make Posting Date field as input field during IW45 (Cancel Confirmation) so that we can overcome closed posting period problem?
Thanks
DM
Edited by: Deepak M on Oct 2, 2009 7:48 AM
Edited by: Deepak M on Oct 2, 2009 7:50 AM
Edited by: Deepak M on Oct 2, 2009 7:50 AM

Hi Deepak,
Ask Finanse, & Material Team to open period. Once it is opened cancel the confirmation nos.
Further the same confirmation can be used to repost the enties in new period.
Regards,
Ramesh

Similar Messages

  • Confirmation cancel - other posting period

    Dear All,
    Can we cancel the Order Confirmation on other date? If yes how, in IW45 all fields are grey out?
    It no, then what to do if the FI period is been closed?
    Plz help
    Thanks
    Deepak

    Hi,
    Yes its possible to cancel the order confirmation. Pls dont worry about the greyed out fields when u execute IW45(Cancel Confirmation). When u execute IW45, type in the order no. and press enter. Then once u are on Cancel Confirmation screen (all greyed out) , press Back button. Now ot will ask you to put in some cancellation text. Press Insert, type in the reason for cancellation and then press End Insertion. Then press back. Again it will ask you if u wanna save the cancellation. Say yes. Now your Order confirmation stands cancel. U can test it by again executing IW41/IW42.
    Hope this solves your problem.
    Saurabh.

  • Network confirmation cancell. thru CN29,when past posting period isnot open

    Hi Gurus,
    I have one query regarding netowrk confirmation. In our scnario, we are confirming network activity/element directly through CN27. Now after confirmation, due to some mistake we are trying to cancel that confimration through CN29 but system gives me error that "posting period is not open". As my network confirmation was done in the month of March'10 and i am trying to cancel it in April'10 that's why system is not allowing me to canel the confimration.
    Now my query is that how to cancel the network confimmation without opening past posting period. I looked into the configuration for network confirmations but there is no setting available to allow cacellation of network confirmation done in posting period which is not open now.
    however in CAT5, we have a option where we can enter cancellation posting date, and system allows to cancel time postring for that period also which is closed now (by putting cancellation posting date belonging to current posting period wihhc is open).
    regards
    Alok Mittal

    I have not verified the same on system, but  It's quite good observation. I think it's standard behavior  in system and could be possible, in CN29 you are not having option to put posting date, so, system is taking date of posting date on which it got posted for reversal. i.e. March 10, but period is closed for that date. so, system is giving you error that period is closed.
    Now coming to CAT5 if you give posting date of March 10, and try to reverse this document system will give you same error of period close. but if you give posting date of period April 10 system will allow to post. Because  current period is open. Reversal program works in SAP based on some logic for different documents. 
    If you wanted to check why system is behaving in that way in that case, compare  both documents ( original posted and reversal document posted in CAT5, check after posting reversal document is there any change done by system to original documents , I understand mostly system put reversal tick mark or  so, in original document and give reference document in new documents )
    Please check and revert back.
    With Regards
    Nitin p.

  • Cancel or reverse the process ordrer confirmation posted in a closed period

    Hi SAP experts,
                              It would be very nice of you if you could solve this issue for me.
                              The issue is -
                               There is a process order created and released for a material on 01.07.2010.Partial confirmation for the order was done on 15.07.2010 but the posting date was entered as 14.06.2010.So the stock for the material got posted on 14.06.2010 which was supposed to be posted on 14.07.2010. Now, if we try to cancel the order confirmation in the current month through CORS , system is giving errors because the posting period is closed .
                               Is there any way to reverse the postings without opening the posting period?
                               How we can open the field for the posting date in the transaction CORS where we can assign new posting date for the cancellation of the order confirmation. Is it possible to enter this new posting date as 01.07.2010 now because the posting period for July is currently open?
    Best regards,
    RAB

    The reason for reversal is that - the goods receipt on the date 14.06.2010 should tally with the goods receipt for the process order created for the month of June 2010 on that particular date as per the daily production report developed for client. In this case, only one process order is created for a material for each month and that is confirmed daily as per the daily production and then confirmed and settled finallly at the end of the month.
    Now the requirement is that the excess goods receipt posted in June 2010 for the process order created for July 2010 should be reversed so that the goods receipts for the June's process order on that particular date for that material match properly.
              Actually , to compensate for this wrong posting done  by the user on 14.06.2010, another confirmation for the same order of July 2010 was done for that material with same qty. with correct posting date(14.07.2010) so that the goods receipts for July 2010 for the material for that process order are proper.
             I am sure you must have clearly understood the issue. Is it possible to cancel the the order confirmation done with posting date 14.06.2010 by giving new posting date as 01.07.2010? Whether this will display proper stock for the material in June as well as July? Kindly confirm.
    Best regards,
    RAB
    Best regards,

  • Posting period issue while deleting a confirmation posted for a limit PO

    Hi ..
    I am facing an issue whiel deleting a confirmation posted for a limit PO.
    Confirmation was posted for a limit PO in SRM and it created a service entry sheet in SAP. If I deleted that confirmation in the same posting period, then it is getting deleted. No issue here.
    But if I deleted that confirmation in the next posting period then the reversal document is going to error in process. RZ20 is showing the error "Positng only possible in periods 2012/2 and 2012/3".
    Posting date of reversal document is current date only and the backend posting period is 2012/3, but still it is failing with this posting period error.
    If I tried to delete a confirmation posted for a normal PO then I could able to delete it even in next posting period by just changing the posting date.
    Why this posting occurs while deleting the limit confirmation, even through the posting date is falls within the backenn posting periiod? Is it like, SAP system is trying to delete the service entry sheet in original posting period? Kindly help.
    I am in SRM 5.0 (server 5.5) SP12.
    Thanks,
    Arun

    OK.
    Well, if the variable is not used in any interval selection, then I would say "something happened to it".
    I would make a copy of the query and run it to check if I get the same problem with period 12.
       -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
    If so, then try removing the variable completely from the query and hardcode restriction to 12.
       -> If problem still persists, I would have to do some thinking.
    If problem is gone, then add the variable again. Check.
       -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
    If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
    Good luck!
    Jacob
    P.S: what fisc year variant are you using?
    Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

  • Error while running a query-Input for variable 'Posting Period is invalid

    Hi All,
    NOTE: This error is only cropping up when I input 12 in the posting period variable selection. If I put in any other value from 1-11 I am not getting any errors. Any ideas why this might be happening?
    I am getting the following error when I try and run a query - "Input for variable 'Posting Period (Single entry, mandatory)' is invalid" - On further clicking on this error the message displayed is as follows -
    Diagnosis
    Variable Posting Period (Single Value Entry, Mandatory) is used as a lower limit (X) and an upper limit () in an interval selection. This limit has the value #.
    System Response
    Procedure
    Enter a different value for variable Posting Period (Single Value Entry, Mandatory). If the value of the other limit is determined by another variable, you can change its value also.
    Procedure for System Administration

    OK.
    Well, if the variable is not used in any interval selection, then I would say "something happened to it".
    I would make a copy of the query and run it to check if I get the same problem with period 12.
       -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
    If so, then try removing the variable completely from the query and hardcode restriction to 12.
       -> If problem still persists, I would have to do some thinking.
    If problem is gone, then add the variable again. Check.
       -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
    If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
    Good luck!
    Jacob
    P.S: what fisc year variant are you using?
    Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

  • Reg: Query Problem for New Posting Period

    Hi Xperts,
    While I try to Map the A/P Invoices with their respective Outgoing Payment,
    I used the following Query and it's Query Printlayout
    SELECT T0.DocNum [Payment#], T0.DocDate [Payment Date],
    T0.CardCode, T0.CardName, T1.InvoiceId, T2.DocNum [AP Inv#],
    T2.NumatCard [Bill No.], T2.DocDate [Bill Date], T1.selfInv,
    T1.SumApplied, T1.WtAppld, T0.NoDocsum 
    FROM  [dbo].[OVPM] T0  INNER  JOIN
    [dbo].[VPM2] T1  ON  T1.[DocNum] = T0.DocNum
    INNER  JOIN [dbo].[OPCH] T2  ON  T2.[DocEntry] = T1.DocEntry
    WHERE T0.Cardname='[%0]' and T0.DocDate='[%1]' and
    T0.DocNum='[%2]'
    I got the above query from our Expert Mr.Sambath only.
    Now what is the problem is the query is retrieving the payment details of old Posting Period only and not the current posting period.
    In detail, I used 'Primary' Series for FY08-09, Period indicator 'Default'
    Now I'm using 'Primary1' Series for FY09-10, Period indicator '0910'
    Thanx in adv.
    Regards,
    Bala

    Hi Bala,
    Looking at your query, it is not query issue ,it is your data issue.
    Please check if you have data in  VPM2  table  which is bank transfer payment method
    Thank you
    Bishal
    Edited by: Bishal Adhikari on Apr 9, 2009 8:48 AM

  • Posting period 005 2020 is not open when perfomr /dbm/cashdesk cancellation

    Hi Expert,
    Currently our SAP DBM on patch7 & SP04 (latest), now i would like to cancel cash document in /dbm/cashdesk and system come out with error as below:
    Posting period 005 2020 is not open
    Message no. F5201
    Diagnosis
    Period 005 of fiscal year 2020 is not open for posting for the variant of posting period 5000.
    System Response
    Processing cannot be continued.
    Procedure
    The error can have several causes. In order to eliminate the error, proceed as follows:
    1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
    2. Check whether the required posting period is open for posting for the variant of posting period 5000 and account type +. Make sure that the period is open for posting.
    To do this, specify a period interval in which the required period for the variant of posting period 5000 and account type + is contained.
    You make these settings in Customizing of Financial Accounting (New) under Financial Accounting Global Settings (New) -> Ledgers -> Fiscal Year and Posting Periods - > Posting Periods -> Open and Close Posting Periods.
    I able to post cashdesk document in customer incoming payment tab and i cannot cancel due to posting period 05 & year 2020 not open.
    Currently we are in 05 2011 not 2020, is any expert can advice where to set cashdesk fiscal year configure?
    I need to open FI period until 05 2020, then my cash document cancellation is successful.
    Thanks
    regards,
    ng chong chuan

    Hi,
    First check the Current period in OMSY trx...for your Comp code..
    Then go to MMPV and enter Comp code, Period & Year
    and execute...
    Ex: if the current period in OMSY for your Comp code is 01,2008
    then you need to enter period 02, 2008 in MMPV trx...
    so, that period 01 will be closed & Period 02 will be opened automatically...
    You need to close periods one by one like this..
    until the period you want use...
    Remember you can not Roll back the closed period
    Be careful in closing the MM period in PRD client.
    Thx
    Raju

  • How to calculate First Date of Posting Period in BEx Query

    Hi,
             I have  2 reporting requirements as follows:
    1) User will either enter a single posting period in a fiscal year or can enter a range of posting periods.
    Based on user selection I need to display three key figures in a report.
    Key figure 1 and Key Figure2 should be the summarized values for each posting period.
    key Figure 3 should be the value on the first date of that particular posting period (in case user selects multiple posting periods i should derive the value of the first date of each posting period).
    2) Also, in another report I need to display only top 8 values  for one key figure in the report.
    Please let me know the method or code required to get this Functionality.
    Thanks in advance.

    First Report
    1. Create Restricted KeyFigure 1 & 2 for the summarized values.
    2. Create a Customer Exit Variable for getting the first date of the posting period, this should be of type Interval. Write code using FM FIRST_DAY_IN_PERIOD_GET to get. Read the selection variable to see the range of posting period and you have to insert that many first dates into this variable.
    3. Create a new Restricted KeyFigure 3 and use the Customer Exit variable created in Step 2
    Second Report
    Use the Top N functionality of BEx and create a workbook. You can set the option Refresh query when the workbook is open so that the data is current when opened.
    Hope this helps.

  • How to substitute a month abbreviation for the posting period in a query

    Hi,
    I have a query that lists the Posting Period (0FISCPER3) characteristic in the rows and key figures across the columns.  Is there a way to display the Posting Period as a month abbreviation instead of a number? 
    So for example, instead of displaying the periods 01, 02, 03, 04... in the rows, I would like to display the abbreviation of the corresponding month, for example Jun, Jul, Aug, Sep... etc.
    Thanks,
    Mustafa.

    Hi,
    Thanks for the suggestions.  If the master data texts are updated for characteristic "0FISCPER3", this would assume that all Company Codes have the same Fiscal Year Variant.  What happens in a situation where there are multiple Company Codes with different Fiscal Year Variants, a case which is common for multinational companies?
    Can such a manipulation be performed in the query itself based on the Fiscal Year Variant?
    Regards,
    Mustafa.

  • Posting Period coming into the rows at the query runtime & couldn't drop it

    Hi All,
    We have a query on an InfoCube that we have copied to the Multiprovider containing two cubes, exact copies of the original cubes.
    Two cubes are one for the previous years and one for the current year.
    Now, the query is copied from original cube to the MultiCube.
    The query looks exactly the same in the Query Designer. But when run in Analyzer or on Web, Posting Period is coming into the rows automatically and in Analyzer, when I double click on the Posting Period to take it away from the report, it doesn't go away. Similarly in web, I do not have a option 'Remove Drilldown from rows', against posting period. I have identified posting period in both the cubes in the MultiCube configuration.
    Thanks in advance for any suggestions that you have.
    Best Regards,
    - Shashi

    hmm, we have now something interesting....
    but this means that you have two structures defined in your query right?
    Is your query cell based? It looks to me that this is the case; you have elements using created using the posting period thus it can be moved to the free chars and must be included in the drilldown.
    Remove the posting period again and perform a check before saving the query; this may give the element defined with your posting period.
    hope this helps...
    Olivier.

  • Block cancellation/creation of billing document on CLOSED posting period

    Hi Experts,
    Currently, user is allowed to cancel/create backdated billing document where period already closed, but it does not release to accounting automatically, due to the period has been closed.
    When account user found out that the accounting document is missing for the billing document, they have to re-open the period and manual release it to accounting, in order to generate the accounting document.
    Therefore, we need the billing document to be blocked for cancellation/creation on CLOSED posting period.
      Is there any settings in stardard SAP to block cancellation/creation of billing document on CLOSED posting period?
    would appreciate your inputs.
    Thanks and Regards,
    N.C.Reddy

    Hi ,
    We have blocked cancellation/ creation of billing document through below  user exit. Below is the progran code also.
    ***INCLUDE RV60AFZC.
    FORM USEREXIT_NUMBER_RANGE_INV_DATE USING US_RANGE_INTERN.
    Example: Number range from TVFK like in standard
    US_RANGE_INTERN = TVFK-NUMKI.
    *{   INSERT         KPDK904773                                        1
    *Block creation or cancellation of billing doc in closed period
    DATA : gv_gjahr TYPE bkpf-gjahr,
           gv_monat TYPE bkpf-monat,
           gv_poper TYPE t009b-poper,
           gv_bukrs TYPE t001-bukrs,
           lv_gjahr TYPE t001b-frye1,
           lv_monat TYPE t001b-frpe1,
           gv_oper  TYPE t001b-frpe1.
      CLEAR : gv_gjahr, gv_monat, gv_poper, gv_bukrs.
      gv_bukrs = vbrk-bukrs.
    IF NOT likp-wadat_ist IS INITIAL.
    *- First determine the Period of the Actual GI date.
      CALL FUNCTION 'FI_PERIOD_DETERMINE'
        EXPORTING
          i_budat              = likp-wadat_ist
          i_bukrs              = gv_bukrs
       IMPORTING
         E_GJAHR              = gv_gjahr
         E_MONAT              = gv_monat
         E_POPER              = gv_poper
       EXCEPTIONS
         FISCAL_YEAR          = 1
         PERIOD               = 2
         PERIOD_VERSION       = 3
         POSTING_PERIOD       = 4
         SPECIAL_PERIOD       = 5
         VERSION              = 6
         POSTING_DATE         = 7
         OTHERS               = 8.
          IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                   WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ELSE.
            CLEAR : lv_gjahr, lv_monat.
            lv_gjahr = gv_gjahr.
            lv_monat = gv_monat.
    *- Once period is determine check whether Period is open or not for 'D' - Customer Account
            CALL FUNCTION 'FI_PERIOD_CHECK'
              EXPORTING
                I_BUKRS                = gv_bukrs
                i_gjahr                = lv_gjahr
                i_koart                = 'D'
                i_monat                = lv_monat
             IMPORTING
               E_OPER                 = gv_oper
             EXCEPTIONS
               ERROR_PERIOD           = 1
               ERROR_PERIOD_ACC       = 2
               INVALID_INPUT          = 3
               OTHERS                 = 4.
              IF sy-subrc <> 0.
               MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ELSE.
    *- Once period is determine check whether Period is open or not for 'S' - All G/L Accounts
                CALL FUNCTION 'FI_PERIOD_CHECK'
                EXPORTING
                  I_BUKRS                = gv_bukrs
                  i_gjahr                = lv_gjahr
                  i_koart                = 'S'
                  i_monat                = lv_monat
               IMPORTING
                 E_OPER                 = gv_oper
               EXCEPTIONS
                 ERROR_PERIOD           = 1
                 ERROR_PERIOD_ACC       = 2
                 INVALID_INPUT          = 3
                 OTHERS                 = 4.
                IF sy-subrc <> 0.
                  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
               ENDIF.
             ENDIF.
         ENDIF.
    ENDIF.
    *- Check Billing Date period is closed or not
    IF kom-fkdat is not initial.
      clear : gv_gjahr, gv_monat, gv_poper.
    *- First determine the Period of the Actual GI date.
      CALL FUNCTION 'FI_PERIOD_DETERMINE'
        EXPORTING
          i_budat              = kom-fkdat
          i_bukrs              = gv_bukrs
       IMPORTING
         E_GJAHR              = gv_gjahr
         E_MONAT              = gv_monat
         E_POPER              = gv_poper
       EXCEPTIONS
         FISCAL_YEAR          = 1
         PERIOD               = 2
         PERIOD_VERSION       = 3
         POSTING_PERIOD       = 4
         SPECIAL_PERIOD       = 5
         VERSION              = 6
         POSTING_DATE         = 7
         OTHERS               = 8.
          IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                   WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ELSE.
            CLEAR : lv_gjahr, lv_monat.
            lv_gjahr = gv_gjahr.
            lv_monat = gv_monat.
    *- Once period is determine check whether Period is open or not for 'D' - Customer Account
            CALL FUNCTION 'FI_PERIOD_CHECK'
              EXPORTING
                I_BUKRS                = gv_bukrs
                i_gjahr                = lv_gjahr
                i_koart                = 'D'
                i_monat                = lv_monat
             IMPORTING
               E_OPER                 = gv_oper
             EXCEPTIONS
               ERROR_PERIOD           = 1
               ERROR_PERIOD_ACC       = 2
               INVALID_INPUT          = 3
               OTHERS                 = 4.
              IF sy-subrc <> 0.
               MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ELSE.
    *- Once period is determine check whether Period is open or not for 'S' - All G/L Accounts
                CALL FUNCTION 'FI_PERIOD_CHECK'
                EXPORTING
                  I_BUKRS                = gv_bukrs
                  i_gjahr                = lv_gjahr
                  i_koart                = 'S'
                  i_monat                = lv_monat
               IMPORTING
                 E_OPER                 = gv_oper
               EXCEPTIONS
                 ERROR_PERIOD           = 1
                 ERROR_PERIOD_ACC       = 2
                 INVALID_INPUT          = 3
                 OTHERS                 = 4.
                IF sy-subrc <> 0.
                  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
               ELSE.
                IF kom-fkdat4(2) <> likp-wadat_ist4(2).
                ENDIF.
               ENDIF.
             ENDIF.
         ENDIF.
    ENDIF.
    *}   INSERT
    ENDFORM.
          FORM USEREXIT_FILL_VBRK_VBRP                                  *
          This userexit can be used to fill fields in VBRK and VBRP     *
          Be aware, that at this time the work areas KUAGV KURGV        *
          KUWEV and KUREV are not filled.                               *
          This form is called from FORM VBRK_VBRP_FUELLEN.              *
    FORM USEREXIT_FILL_VBRK_VBRP.
    Example: change Tax country
    VBRK-LANDTX = T001-LAND1.
    ENDFORM.
    *eject

  • While cancelation of migo  i get error posting period 07-08 company code

    while cancelling migo i get error msg posting period 07-08 company code my migo is dated 23.07.2010 pls help

    Hi,
    Please check what fiscal year calculation yu are using in the system ! is it from April to March or from January to december...
    as well check which period open currently in the system OMSY is TCode or MMRV.
    as well please search SDN portal for same kind of questions.
    Regards,
    Ninad Kshirsagar

  • Error that "specify a value for variable posting period (single value entry

    hi
    My query is running testing fine in RSECADMIN under some username..but when i try and open it using analyzer (under same username) it gives me error that "specify a value for variable posting period (single value entry, mandatry)" it does'nt even asks to enter variable values and gives this error message.
    However the same query appears to be working fine under different username.
    plz advise.

    Hi Abhinav,
    Just do one thing compare the Roles of two different users for which Query is getting executed and not.
    Check the Object S_RFC.
    Compare the Objects detail for Both the Users.
    Please Assign points if useful.
    Regards,
    Rajdeep.

  • Can we open and close Posting period for HR module

    Dear All ,
    Can someone please tell me is there any option available to open and close Posting period for HR Module.We have In Finance and MM.
    Cheers
    Balaji Dhanavel

    check
    the report RPCIPE00 useing SE38
    can u be some wht clear of ur query once

Maybe you are looking for

  • A way to search System Files and by File Name as default?

    Hello. Is there a way I can make the default search both include searching by File Name and searching System Files? I know I can make a saved search, but this just is one extra step. I'd like to the default behavior of the Finder be to search system

  • Mac pro with windows - unable to get from mac to windows..

    can not get the partition up on booting up for mac and windows only mac as an option however windows is visible in bootcamp? What can i do to fix this and how?

  • Database access tutorial doesn't add actionOutputs when action is added

    I've installed weblogic portal 10.3 Potential issue: The help shipped with 10.3 in the path %BEA_HOME%\tools\eclipse_pkgs\2.0\eclipse_3.3.2\eclipse\plugins is org.eclipse.help.base_3.3.1.v20070813_33x.jar not ...base_3.3.2.v... In the workshop tutori

  • CUCM 7 software upgrade

    Hi      There We are going to upgrade our CUCM7.1.3 to CUCM 7.1.5. We have 1 pub and 2 subs. According to the Cisco document, once the software being installed, we just need to switch the version and the system will start and running with the new ver

  • How to set royalties in Oracle

    Hello people - I had a case that wanted to run by y'all and get some feedback. See, my company manufactures devices which require to pay for royalties to vendors at the moment the SO gets shipped out. They way they do it now is a bit complicated and