How to hide componant row of BOM while creating sales order OR AR Invoice

Dear expert
my client wants to create Sales order with Sales BOM, but they do not want to see componant product while create sales order or AR invoice they want to see only parent items.
Please help me asap

Hi,
check below link
Avoid printing child items of Sales BOM in AR Invoice
Regards
Deepak Tyagi

Similar Messages

How to manual maintain TAX condition value while creating sales order

Hi
I am creating one Tax condition suppose JLST without access sequence .
while creating sales order I am manually maintain the % value of TAX. suppose it is 1%
then I see It show some value in TAX .
save that sales order & creating delivery document for that but when I create Invoice its show error.
" Tax code in procedure CMTAXP is invalid ".
I know the configuration only for Tax condition with vk11 condition record .
BUT now I want to maintain TAX condition at the time of creating sales order.
so I remove the access sequence of that condition .
but It shows tax code error while billing.
My main question is that If i maintain condition record while creating sales order then how i can assign Tax code .
Can it is possible ?
if yes then How?
please help me.
thank you

Hi,
The "straight-forward" answer for Tax Code creation is contact the FI consultant. He shall help you, by creating Tax codes.
I have tested, with creating a tax cond type (copy of MWST) & manually entering values. I can create Sorder, Dlv and Bill but I cannot create an Accounting document. That is because of every line (amount) a Tax code is necessary.
I THINK, you can NOT have manually filled tax codes; access sequence is needed to get the tax value (%) and the Tax code from the condition record.
There is lot of material on the web to understand Tax classification, code etc. etc. See a useful link below -
http://www.sapgeek.net/2010/04/sd-determines-tax-code/
In short Tax code is a must and take the help of your FI consultant for the configuration of the same.
BTW - Tax code is already made created for MWST, therefore I suggested that you can use MWST. Furthermore, you can change the values corresponding to Tax codes in FTXP.
But if you are a beginner in these things, better take help.

How to change the status of material while creating sales order via BDC

Hai.
In BDC while creating sales order( va01 posting ) it is stucking up in middle saying material is new. I.e Sales order (va01) is not getting created because of material status is new . I want to create sales order (va01) even material status is new.
pls give me out the solution. Points will be rewarded.
thanks & regards,
sami.

Hi,
If you drag the line item a little towards the right side, you will find a filed material entered. The one you see in the material filed on sales order over view screen is the one determined. You can as well double click and see the fields material entered and material determined.
Is there anything else you are expecting to see as part of analysis ?
Regards
Sadhu Kishore

How to avoid XVBPA line item values while creating sales order

Hi Friends
I am creating Sales order using function module IDOC_INPUT_ORDERS, for that I am passing partner details through segment E1EDKA1.If I pass the same partner details(Partner number, name1,name4,city,postel code) which is same like customer master,
I can able to book the order and entries are coming only one time in VBPA table(Header Item level).But if I change any value for the particular partner in the Input(For example Name4, there is no value in customer master but I added through program).Now its creating an order but its showing the entered partner informations in header level.When I checked the same in line item level, its not picking the values from header, its picking the values from customer master for that particular partner.
So this line item also coming in VBPA table, because its different from header data.
Anyone guide me, how to avoid this problem while booking order through program.
Thanks
Gowrishankar

I am updating Ship-To-Party value in segment E1EDKA1 and calling IDOC_INPUT_ORDERS function module to create the sales order.
In this case for the particular partner there is no NAME4 value in KNA1, I am passing some value through this segment E1EDKA1.
So its creating an order with this new addresses , so its generating new ADRNR in VBPA header level.Thats fine.But the same time
its not copying the same value from header to line item.
In Line item level again its picking the address details from KNA1 for the particular partner number.So its showing Blank value in NAME4 field of line items.Its creating and spllitting issue, while creating delivery.
Thanks
Gowrishankar

How to block the material qty to 1 while creating sales order (VA01)?

Hi All,
Scenario : We have 20 Materials each with 100 qty in Plant. In the sales order we should have all the 20 materials with qty one. The sales order should throw an error if the material qty is more than 1 and should not allow to create a sales order.
so is there any transaction code where we can block the entire material qty to 1 from the same plant while creating sales order?
Note: We should not set in MM01 "Minimum order qty". Assume we have 100 material in plant we can't set for each material one by one "minimum order qty".Instead of that is there any option to set the whole material qty to 1 as minimum while creating sales order?
Kindly guide me how to proceed.
Thanks,
Renjith

If you have access to idoc before calling the processing Function module, Adding header text segments E1EDKT1 and E1EDKT2 to the idoc will create the header text.
Regards
Sridhar

How to restrict the order reason in Tcode Va01 while creating sales order

Hi Gurus,
My requirement is
while creating sales order in VA01
if order type is Zvol
than the list of order reasons has to be restricted.
Now 15 are coming from OVAU tcode
I need only 5 from these.
Thanks & Reagrds
kals.

Hi,
By doing the user exit in IW32 we achieved the requirement of restriction of maintenance order TECO functionality if any Service Entry sheet pending with reference of maintneance order.
regards
JKM

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Hi error while creating sales order

hi
i am getting 'not able to save' message while i am creating sales order.
how should i proceed to know where is the problem???
i tried debugging but it is taking lots of time, is there any other way i can know the reason for this error in standard code.
there is no wrong data entry while creating sales order.
i just want to know what are the ways to know where is the problem in the standard code.
thanx
rocky

hi ,
try too create a sales order after that check transaction code ST22 U WILL FIND AN SHORT DUMP then check in the source code extract an pointer will be visible where the error is coming and it will also show the program name , please read the dump analysis care fully
srinivas

Automatic creation of settlement rule while creating sales order

Hi Friends,
Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
thanks
bobby

Hi,
Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
and write the form routine in Program named 'ZRGGBS000'
The code is below ,
*&      Form U902
   Automatic Generation of Settlement Rule For WBS and Company 4180
FORM u902.
Exit For Automatic Settlement Rule Creation for WBS Billing elements
IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
    DATA   lv_proj TYPE ps_pspid.
    lv_proj = proj-pspid.
    EXPORT lv_proj TO MEMORY ID 'PSPID'.
Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
    SUBMIT ygps_cjb1exec AND RETURN.
ENDIF.
ENDFORM.                                                    "u902
*& Program YGPS_CJB1EXEC
PROGRAM ygps_cjb1exec.
   Automatic Generation of Settlement Rule For WBS and Company 4180
Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
DATA: bdcdata_wa TYPE bdcdata,
      bdcdata_tab TYPE TABLE OF bdcdata,
      itab TYPE TABLE OF bdcmsgcoll.
DATA :lv_currm LIKE bkpf-monat,
      lv_curry LIKE bkpf-gjahr,
      lv_prevm LIKE bkpf-monat,
      lv_prevy LIKE bkpf-gjahr,
      lv_proj TYPE ps_pspid,
      lv_mode TYPE c,
      lv_time TYPE sy-uzeit.
DATA :g_datfm            LIKE usr01-datfm,
      g_dd(2)            TYPE c,                         " Day
      g_mm(2)            TYPE c,                         " Month
      g_yyyy(4)          TYPE c,                         " Year
      g_sydatum(10)      TYPE c.
IMPORT lv_proj FROM MEMORY ID 'PSPID'.
lv_mode = 'N'.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'PRZB-VARIANT'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'PRZB-VARIANT'.
bdcdata_wa-fval = 'ZGPS0001'.
APPEND bdcdata_wa TO bdcdata_tab.
CALL FUNCTION 'GET_CURRENT_YEAR'
EXPORTING
    bukrs = '4180'
IMPORTING
    currm = lv_currm
    curry = lv_curry
    prevm = lv_prevm
    prevy = lv_prevy.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-FROM'.
bdcdata_wa-fval = lv_currm.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-GJAHR'.
bdcdata_wa-fval = lv_curry.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VARC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'RKPSEL00'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'CN_PROJN-LOW'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PROJN-LOW'.
bdcdata_wa-fval = lv_proj.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_NETNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_MATNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '/00'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=SAVE'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VBAC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSPO1'.
bdcdata_wa-dynpro   = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=YES'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-BATCH'.
bdcdata_wa-fval = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-TEST'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=RUN'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKABA'.
bdcdata_wa-dynpro   = '0210'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-JNAME'.
bdcdata_wa-fval = 'CJB1_EXEC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_SUBSCR'.
bdcdata_wa-fval = 'SAPLKABA'.
APPEND bdcdata_wa TO bdcdata_tab.
Extract the date format from the user settings
PERFORM f_get_dateformat CHANGING g_datfm.
Changing the current date format to User Profile Date Settings
PERFORM f_format_date USING   g_datfm
                              sy-datum+4(2)
                              sy-datum+6(2)
                              sy-datum+0(4)
                     CHANGING g_sydatum.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STDAY'.
bdcdata_wa-fval = g_sydatum.
APPEND bdcdata_wa TO bdcdata_tab.
lv_time = sy-uzeit + 30.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STTME'.
bdcdata_wa-fval = lv_time.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-PRIKZ'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=TAKE'.
APPEND bdcdata_wa TO bdcdata_tab.
Calling Transaction 'CJB1' for creating settlement rule
CALL TRANSACTION 'CJB1' USING bdcdata_tab MODE lv_mode .
IF sy-subrc = 0.
ENDIF.
*&      Form F_GET_DATEFORMAT
      This subroutine returns the date format in the user setttigs
     <--P_G_DATFM Date Format
FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
WHERE bname = sy-uname.
ENDFORM.                    " F_GET_DATEFORMAT
*&      Form F_FORMAT_DATE
      This subroutine returns the date as per the user settings
     -->P_G_DATFM Date Format
     -->P_G_MM Month
     -->P_G_DD Day
     -->P_G_YYYY Year
     <--P_G_DATE Date
FORM f_format_date USING    p_g_datfm
                            p_g_mm
                            p_g_dd
                            p_g_yyyy
                   CHANGING p_g_date.                       "#EC *
CONSTANTS: c_dot VALUE '.',
             c_slash VALUE '/',
             c_dash VALUE '-',
             c_1 VALUE '1',
             c_2 VALUE '2',
             c_3 VALUE '3',
             c_4 VALUE '4',
             c_5 VALUE '5',
             c_6 VALUE '6'.
DATA: l_day(2),
        l_month(2).
l_day = p_g_dd.
l_month = p_g_mm.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_month
    IMPORTING
      output = l_month.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_day
    IMPORTING
      output = l_day.
CASE p_g_datfm.
    WHEN c_1.
      CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_2.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
       SEPARATED BY c_slash.
    WHEN c_3.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
          SEPARATED BY c_dash.
    WHEN c_4.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_5.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_slash.
    WHEN c_6.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dash.
ENDCASE.
ENDFORM.                    " F_FORMAT_DATE
thanks
bobby

Runtime error while creating sales order in VA01

Dear all,
In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
application patch level for both production and development is same.
can any one suggest the solution please

Please note the error details
Runtime Errors         SYNTAX_ERROR
Date and Time          07.01.2010 17:43:06
Short text
Syntax error in program "RK2LSFOC ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RK2LSFOC " in include "RK2LSFOC
" in
line 128:
"No component exists with the name "KWBRUM". ."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP* "
Error in the ABAP Application Program
The current ABAP program "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RK2LSFOC ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program RK2LSFOC :
"No component exists with the name "KWBRUM". ."
|    " "

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order what it means when we give Yes or No. how pegging flows
Regards
virender

Virender,
Can you be a bit more specific about ".....generally we assigned yes or no while creating sales order....." Exactly what field(s) did you 'assign'? Screenshots would be helpful.
With respect to pegging; in general, ATP has very little to do with pegging. Pegging is more of a planning concept, and not an 'availability checking' concept. There are a few exceptions in APO, but they are not commonly implemented.
Can you elaborate about exactly what you want to know with respect to 'pegging' and ATP?
Best Regards,
DB49

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

Error while creating sales order

while creating sales order for a particular plant there is error coming
NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
PLANTXVBAK-VKBUR.
Intailly I have check the no series we have internal no series for all plant,the
number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
kindly guide me for the same.

Hi Sanjay
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key Start Number range End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0
The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
Regards
Naren

Error while create sales order

Hi,
Please help.
I am facing error while create sales order.
No item category available (Table T184 OR VERP )
Message no. V1320
Diagnosis
No item category could be determined for the combination OR VERP .
System Response
The system does not allow further processing of this item.
Procedure
Check the entries in table T184 by means of which item category determination is controlled.
If you do not have the authorization to do this yourself, contact your system administrator.

Hi,
Check in spro whether Item categorygroup VERP is assigned to sales document type.if not assign.
Path
SPRO-SD-sales-sales douments-sales document item-assign item categories.

End of Valid Logistic Calender error while creating Sales Order

Hi,
While creating Sales order in VA01 the following error message comes for particular material code for a particular site only:
24.01.2202 date comes after end of valid logistics calendar. (Please
correct)
Message no. 61062
Can anyone suggest on the same.
Regards
Nilofer

Hi,
The input value given in Sales order is " Req Delivery date: 31.03.2012", but the error comes with the below date such as
"24.01.2202 date comes after end of valid logistics calendar.(Please correct)"
We also face one more error such as
" Incorrect index structure for table XMVERF_POS/0000224110/000040 ".
From where system is taking 24.01.2202 date?

How to hide componant row of BOM while creating sales order OR AR Invoice

Similar Messages

Maybe you are looking for