Header Level Data In Sales Doc

Hi Gurus'
I know that header level data is applicable to all the items in the sales document. But is this always the case? Is there a case where header level data is not applicable to all items in the sales order?
i want to know so i can test it on the system.
thanks

Amit,
Header level information may not be same as item level information. Few examples:
1. Business data (Incoterms, Payment terms)
Based on your configuration, in VOV7, item category, if you activate business item. Then you can have different incoterms etc. at header level and item level in a sales order.
2. Partners
As mentioned by JM, if you set up partner determination, assigned to sales document type and item category, both having SH partner function; then in the sales order, you can have different SH at header and different SH at item levels.
3. Division
Based on configuration, VOV8, sales document type, field item division if you activate this, then the division at header and item can be different.
In the sales order, header division will come from the division given in the initial screen VA01
and in the item, the division will populate from the material master 's division.
TW

Similar Messages

BADI for sales order header level data

Is there any BADI which will give me the sales order header level data? I need net price of the sales order in header level. KOMK structure does not contains the net price value.

My requirement is:
I am writing a pricing routine for calculating ZSMR condition value in sales order header level. The formula for calculating is (NET PRICE / NET SALES COST) / NET PRICE.
I can't use VBAK because I have not saved the sales order yet. I need to use some structure.
Which structure contains the net price of the sales order in header level. KOMK structure does not contains the net price value.
Edited by: dossgs on May 21, 2010 4:08 PM

Dont allow to change item level data in sales order.

Hi all,
I have a requirement in which, users should not be allowed to change item level data or not allowed to add any new items in sales order on a certain condition. But they should be allowed to change the header level data.
How can i achieve this.
Can anyone help me?

Hi,
Check below exit.
MV45AFZZ and in form USEREXIT_MOVE_FIELD_TO_VBAP.
Here check for ur validation, If passes then CHECK variable SVBAP-TABIX. If it is 0 then item is created. If it is GT 0 then item is changed. Other way could be...
select data from VBAP for each sales document and item in xvbpa internal table.
If for any item u don't have data in VBAP table that means u r adding that item. So issue error message.
*       FORM USEREXIT_MOVE_FIELD_TO_VBAP                              *
*       This userexit can be used to move some fields into the sales *
*       dokument item workaerea VBAP                                  *
*       SVBAP-TABIX = 0: Create item                                 *
*       SVBAP-TABIX > 0: Change item                                 *
*       This form is called at the end of form VBAP_FUELLEN.          *
Thanks,
Vinod.

What is Header level data and item level data? Please elaborate.

What is Header level data and item level data? Please elaborate.
Details:
EKKO is Purchasing Document Header; what is purchasing Document Header? who,what and where can i look for this data.
EKPO is Purchasing Document Item; what is Purchasing document item means?
what is item level data means?
When you take the Senario of SRM and ECC; where the purchase data is maintained primarily in SRM or ECC?
Thanks in advance. I will assign the points only to the valuable information.
York.

Hi York,
You are right in stating EKKO as header and EKPO as line item data. They are maintained in ECC.
Now for the details about the data:
In SAP every transaction is referred to as a document. In this case you are talking about a purchase document. Now what does purchaing document contain? I will contain information like: Who is the vendor? When was the transaction done? what was bought? What is the quantity of each item bought?
Whatever is applicable across the document is called header data... and what is applicable for each item is called line item data. In this case
1. Header data would be the vendor, date of transaction, purchaing organization ... etc.
2. Line item data would be the item details, the quantity of the item, the unit price of each item ...etc.
Hope this helps.
Best regards,
Kazmi

Header level data

Hi SAP Prof,
1.what are the possible questions in Header level data, Item Level data and scheduline data.

Dear Rajesh Johnston,
I would request you to spend some time with ths link. It will help you to get the overview of SAP SD module. http://sap-img.com/sap-sd.htm
If you go to the search on SDN forum you will find lot of help on the similar data.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

KNA1 is a header level data or item level data ?

How should we treat KNA1 ?
As a header data table or
Item Data table ?

Hi,
KNA1 is master data table stores information about customers.it will update thru XD01/XD02 tcodes or FD01/FD02..etc.
Master data will be used to create transactional data.
Once we created master data means,normally we dont change.like employees creation,vendor creation..etc
When it comes transactional data we have concept of header and item level.
suppose sales order is transactional data.conatins VBAK as header level, VBAP as item level data.
Header data contains main information to all the items like shipto party sales order creation date ,who created sales order,sales order type..etc.
Item level contains what material,order qty..etc.
we can call Transactional data as frequently changing data.Like when ever customer needs some item from company means we create sales order for that item.so we call transactional data as daily basis change data.
Please reward if useful.
Thanks
Sivaparvathi
Message was edited by:
Siva Parvathi

Adding Variant in Header Level in the Sales Order

Field "Card Verification Value" (CVV) is part of the Standard from Support Package SAPKH47028 onwards. But if you like you can use a variant for screen SAPMV45A4440 and set
field "Card Verif.Code" to invisible in this variant.
This is the reply from SAP after implementing the new support pack. Now there is an additional field in VA01 that I am trying to remove.
I can add the variant in Table Settings but that is on Item Level in the Sales Order (VA01). How do I do it in Header Level?

Hi,
Go to SHD0 ,write down the Transaction code , transaction variant then go to Tab " With Processing'.
Now you will be in T Code VA01 ,press enter and you will get all the variants maintained in Header Level.
Now you can activate / deactivate as per your requirement.
Best Regards,
Ankur

Smart form for different header level data

Hi,
I need to design a smart form,in th samart form i have 2 header records and for each header reocrd again 10 item records.
My form shd print with fst header record and its item records and after ending fst header record details it shd give 2nd header record and its item records.
For example I have Header records A and B
A have 1 2 3 4 5 item records and
B have 7 8 9 10 11 item records
My form shd be
A----
1
2
3
4
5
b----
7
8
9
10
11
Any inputs please
Regards
Rasheed
Edited by: Rasheed salman on Mar 19, 2009 5:33 PM

You can use the SORT to have different header.
You must be having some indicator in your ITEM table to distinguish different set of data.
In the TABLE node, Under the DATA tab, give your field in the Sort Criteria.
Select the check box Event on Sort Begin.
This will create a new node under the HEADER and MAIN area of your table. In this Node, you can put your Header to have it different for different set of records.
Like:
MAIN window
.. TABLE with sort of field1
.... HEADER
.... FIELD1 sort begin "use this for Header
.... MAIN
Regards,
Naimesh Patel

Billing plan (Downpayment) for saved and open sales orders at header level?

Hi gurus,
I have configured billing plan in my SD environment at Item Level.
I want to change it to header level.
Questions:
1- When I make the changes to update the system to have billing plan at header level for future sales orders, is that possible for me to change all my saved orders and open orders with the new settings so that I can also have those saved and open orders with a billing plan at item level?
2- If that scenario is not possible, could we for example copy the data of a previously saved or open sales order into a new sales order with the new customizing (Billing plan at Header level?)
Thanks for your input
Kind regards
Chris

Hi
I am afraid you cannot do that converstion for the existing orders. BP at header level are enabled at teh document type level, while BP at item level is done at item category. So both are independent. Mostly it is advisabel to use BP at item level only.
If you are already using item level BP, and want to mvoe to header BP, then only future transactions can be executed with BP at header level. Existing item level BPlans will remain so in the system.

Clearing Sales Tax at Header Level in an Order

Hi,
I have a requirement to not charge any tax on an order if the credit card used on the order is a government credit card. Currently I have implemented this logic in USEREXIT_SAVE_DOCUMENT_PREPARE. I am able to clear out the sales tax at the line level but this change does not reflect at the header level. I have to manually click on update pricing to zero out the tax displayed at the header level. I could not find a variable to tap into header level pricing condition and tax value field.
I would greatly appreciate if any one can give me some pointers on where to look for header level data for tax. Also, is there any better user exit to implement this functionality.
Folliwing is the code I am using to clear out line item level tax:
          LOOP AT XKOMV INTO WA_XKOMV WHERE KSCHL EQ 'UTXJ'.    "GET THE TAX CONDITION
              CLEAR WA_XKOMV-KWERT.                               "Set the TAX to 0
              CLEAR WA_XKOMV-KAWRT.
              CLEAR WA_XKOMV-KBETR.
              MODIFY TABLE XKOMV FROM WA_XKOMV
                TRANSPORTING KWERT KAWRT KBETR.
          ENDLOOP.
          LOOP AT XVBAP INTO WA_XVBAP.    "GET THE TAX VALUE
              CLEAR WA_XVBAP-MWSBP.                               "Set the TAX to 0
              MODIFY TABLE XVBAP FROM WA_XVBAP
                TRANSPORTING MWSBP.
          ENDLOOP.
Thanks,
Paresh

Hi,
In the case of sales cycle, All the item level taxes are summirised and come to the header level. So we can't find the conditions at header level for taxes. Check the user exit , because, the values are already moved to the header level structure and then you are clearing the item level taxes. I hope thats why the changes are not reflected in header level.
Regards,

Cannot find sales doc type data in my report on the multiprovider

hai everone,
I'm doing report on the multiprovider which is connected to different ods's i'm getting the data for all the fields except for 'sales doc type'.I could see the data for it in the ods on which the multiprovider is built but could not find the data in the report.Can any one suggest me how to get the data for sales doc type into my report.
Urgent..

yeah listcube is a TCODE to check the data in the cube. run the code and enter the same selections that you would be doing on a query to see and see if it returns any data. if it does, then the problem is with the identification. Most of the times create recommendations work like a charm. But just go into the chars and see if the IO in question has been checked against the ODS that aint returning any records.

Profit Center at header level in sales order

Hi Friends,
Is it possible to have profit center entered at header level in a sales order. If yes then where.
Regards,
Wasim.

No, profit center is always assigned at item level.
One of the reason could be, items in a sales order can have different profit centers, hence assigning at header level will impact all the items.
Regards

BAPI_SALESORDER_CHANGE - Want to change the Ship-to-party at header level

Hi
I want to change the Ship-to-party at header level in the Sales Order created. I tried using the BAPI BAPI_SALESORDER_CHANGE as shown below.
When I run the program I get the log as Sales Order 45 saved succesfully. However, I don't find the SO changed. Apart from this I get an Express Message saying the Updation failure. Not sure of what'z wrong here.
Pls help
thanks
girish
REPORT ZBAPI_SALESORD_CHANGE.
data : zBAPISDHD       type BAPISDH1,
       zSALESDOCUMENT type BAPIVBELN-VBELN.
data : zORDER_ITEMS_IN     like /AFS/BAPISDITM occurs 0 with header line,
       zORDER_SCHEDULES_IN like /AFS/BAPISDSCHD occurs 0 with header line,
       zORDER_PARTNERS like BAPIPARNR      occurs 0 with header line,
       zRETURN         like BAPIRET2 occurs 0 with header line,
       so_no           type BAPIVBELN-VBELN,
       zORDER_HEADER_INX    TYPE BAPISDH1X,
       zPARTNERCHANGES like BAPIPARNRC occurs 0 with header line.
clear : zBAPISDHD.
so_no = '0000000045'.
data : l_comp_qty like zORDER_ITEMS_IN-COMP_QUANT.
l_comp_qty = 10.
zBAPISDHD-SALES_ORG = 'BP01'.
zBAPISDHD-DISTR_CHAN = '02'.
zBAPISDHD-DIVISION = '01'.
zORDER_HEADER_INX-UPDATEFLAG = 'U'.
zORDER_HEADER_INX-SALES_ORG = 'X'.
zORDER_HEADER_INX-DISTR_CHAN = 'X'.
zORDER_HEADER_INX-DIVISION = 'X'.
Ship to pary
zORDER_PARTNERS-PARTN_ROLE = 'WE'.
zORDER_PARTNERS-PARTN_NUMB = 'BPAFS0007'.
append zORDER_PARTNERS.
zPARTNERCHANGES-DOCUMENT = '45'.
zPARTNERCHANGES-ITM_NUMBER = '10'.
zPARTNERCHANGES-UPDATEFLAG = 'U'.
zPARTNERCHANGES-PARTN_ROLE = 'WE'.
zPARTNERCHANGES-P_NUMB_OLD = 'BPAFS0001'.
zPARTNERCHANGES-P_NUMB_NEW = 'BPAFS0007'.
append zPARTNERCHANGES.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    SALESDOCUMENT               = so_no
    ORDER_HEADER_IN             = zBAPISDHD
    ORDER_HEADER_INX            = zORDER_HEADER_INX
SIMULATION                  =
BEHAVE_WHEN_ERROR           = ' '
INT_NUMBER_ASSIGNMENT       = ' '
LOGIC_SWITCH                =
NO_STATUS_BUF_INIT          = ' '
TABLES
    RETURN                      = zRETURN
ORDER_ITEM_IN               =
ORDER_ITEM_INX              =
    PARTNERS                    = zORDER_PARTNERS
    PARTNERCHANGES              = zPARTNERCHANGES.
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
SCHEDULE_LINES              =
SCHEDULE_LINESX             =
ORDER_TEXT                  =
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
data : s_BAPIRET2 like BAPIRET2.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'
importing
return = s_bapiret2.

Thanks Prashanth. It worked !!!!!!!!!!!!!
Now I am facing another type of problem. The requirement is to change the Sales Order Item Quantity. I basically planned to update the quantity of Schedule Item which needs to be changed. When I run the below code, it works and says the Sales Order changed succesfully. However I get an express message saying the Database update failure. I don't get any sort of technical information.
Appreciate if you could help me finding the error.
Thanks
regards
girish
Note --> I am trying to change the Quantity for 2 line item in SO '56' to 40 Units.
REPORT ZBAPI_SALESORD_CHANGE.
data : zBAPISDHD       type /AFS/BAPISDHD,
       zORDER_HEADER_INX    TYPE /AFS/BAPISDHDX,
       zSALESDOCUMENT type BAPIVBELN-VBELN.
data : zORDER_ITEMS_IN     like /AFS/BAPISDITM   occurs 0 with header line,
       zORDER_ITEM_INX     like /AFS/BAPISDITMX occurs 0 with header line,
       zORDER_SCHEDULES_IN like /AFS/BAPISDSCHD occurs 0 with header line,
       ZSCHEDULE_LINESX    LIKE /AFS/BAPISDSCHDX occurs 0 with header line,
       zORDER_PARTNERS like BAPIPARNR      occurs 0 with header line,
       zRETURN         like BAPIRET2 occurs 0 with header line,
       so_no           type BAPIVBELN-VBELN,
       zPARTNERCHANGES like BAPIPARNRC occurs 0 with header line.
data : l_comp_qty like zORDER_ITEMS_IN-COMP_QUANT.
data : g_qty like /AFS/BAPISDSCHD-REQ_QTY.
g_qty = 40.
l_comp_qty = 40.
clear : zBAPISDHD.
so_no = '0000000056'.
zBAPISDHD-REFOBJTYPE = '/AFS/ORDER'.
zBAPISDHD-SALES_ORG = 'BP01'.
zBAPISDHD-DISTR_CHAN = '02'.
zBAPISDHD-DIVISION = '01'.
zBAPISDHD-PMNTTRMS = '0001'.
zORDER_HEADER_INX-UPDATEFLAG = 'U'.
zORDER_HEADER_INX-SALES_ORG = 'X'.
zORDER_HEADER_INX-DISTR_CHAN = 'X'.
zORDER_HEADER_INX-DIVISION = 'X'.
zORDER_HEADER_INX-PMNTTRMS = 'X'.
**********ITEM ***************************************
zORDER_ITEMS_IN-ITM_NUMBER = '00020'.
zORDER_ITEMS_IN-MATERIAL = 'F1202'.
zORDER_ITEMS_IN-PLANT = 'BP01'.
zORDER_ITEMS_IN-ITEM_CATEG = 'TAS'.
zORDER_ITEMS_IN-SHIP_POINT = 'BP01'.
zORDER_ITEMS_IN-COMP_QUANT = l_comp_qty.
zORDER_ITEMS_IN-TARGET_QTY = l_comp_qty.
zORDER_ITEMS_IN-TARGET_QU = 'ST'.
append zORDER_ITEMS_IN.
zORDER_ITEM_INX-ITM_NUMBER = '00020'.
zORDER_ITEM_INX-UPDATEFLAG = 'U'.
zORDER_ITEM_INX-MATERIAL = 'X'.
zORDER_ITEM_INX-PLANT = 'X'.
zORDER_ITEM_INX-ITEM_CATEG = 'X'.
zORDER_ITEM_INX-SHIP_POINT = 'X'.
zORDER_ITEM_INX-COMP_QUANT = 'X'.
zORDER_ITEM_INX-TARGET_QTY = 'X'.
zORDER_ITEM_INX-TARGET_QU = 'X'.
append zORDER_ITEM_INX.
*********SCHEDULE LINE******************************
refresh zORDER_SCHEDULES_IN.
clear zORDER_SCHEDULES_IN.
zORDER_SCHEDULES_IN-ITM_NUMBER = '000020'.
zORDER_SCHEDULES_IN-SCHED_LINE = '0001'.
zORDER_SCHEDULES_IN-REQ_DATE = '20070525'.
zORDER_SCHEDULES_IN-DATE_TYPE = '1'.
zORDER_SCHEDULES_IN-SCHED_TYPE = 'CS'.
zORDER_SCHEDULES_IN-GRID_VALUE = 'BLK2728'.
zORDER_SCHEDULES_IN-REQ_CATEGORY = '1DE'.
zORDER_SCHEDULES_IN-REFOBJTYPE = '/AFS/ORDER'.
zORDER_SCHEDULES_IN-REQ_QTY = g_qty.
append zORDER_SCHEDULES_IN.
refresh ZSCHEDULE_LINESX.
clear ZSCHEDULE_LINESX.
ZSCHEDULE_LINESX-ITM_NUMBER = '000020'.
ZSCHEDULE_LINESX-SCHED_LINE = '0001'.
ZSCHEDULE_LINESX-UPDATEFLAG = 'U'.
ZSCHEDULE_LINESX-REQ_DATE = 'X'.
ZSCHEDULE_LINESX-DATE_TYPE = 'X'.
ZSCHEDULE_LINESX-SCHED_TYPE = 'X'.
ZSCHEDULE_LINESX-GRID_VALUE = 'X'.
ZSCHEDULE_LINESX-REQ_CATEGORY = 'X'.
ZSCHEDULE_LINESX-REFOBJTYPE = 'X'.
ZSCHEDULE_LINESX-REQ_QTY = 'X'.
append ZSCHEDULE_LINESX.
CALL FUNCTION '/AFS/BAPI_SALESORD_CHANGE'
EXPORTING
    SALESDOCUMENT               = so_no
    ORDER_HEADER_IN             = zBAPISDHD
    ORDER_HEADER_INX            = zORDER_HEADER_INX
SIMULATION                  =
BEHAVE_WHEN_ERROR           = ' '
INT_NUMBER_ASSIGNMENT       = ' '
LOGIC_SWITCH                =
TABLES
    RETURN                      = zRETURN
    ORDER_ITEM_IN               = zORDER_ITEMS_IN
    ORDER_ITEM_INX              = zORDER_ITEM_INX
    ORDER_SCHEDULE_LINES        = zORDER_SCHEDULES_IN
    ORDER_SCHEDULE_LINESX       = ZSCHEDULE_LINESX.
PARTNERS                    =
PARTNERCHANGES              = zPARTNERCHANGES
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
ORDER_TEXT                  =
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
*CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
   SALESDOCUMENT               = so_no
   ORDER_HEADER_IN             = zBAPISDHD
   ORDER_HEADER_INX            = zORDER_HEADER_INX
TABLES
   RETURN                      = zRETURN
   ORDER_ITEM_IN               = zORDER_ITEMS_IN
   ORDER_ITEM_INX              = zORDER_ITEM_INX
   PARTNERS                    = zORDER_PARTNERS
   PARTNERCHANGES              = zPARTNERCHANGES
PARTNERADDRESSES            =
ORDER_CFGS_REF              =
ORDER_CFGS_INST             =
ORDER_CFGS_PART_OF          =
ORDER_CFGS_VALUE            =
ORDER_CFGS_BLOB             =
ORDER_CFGS_VK               =
ORDER_CFGS_REFINST          =
SCHEDULE_LINES               = zORDER_SCHEDULES_IN
SCHEDULE_LINESX              = ZSCHEDULE_LINESX.
ORDER_TEXT                  =
ORDER_KEYS                  =
CONDITIONS_IN               =
CONDITIONS_INX              =
EXTENSIONIN                 =
data : s_BAPIRET2 like BAPIRET2.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
importing
return = s_bapiret2.

Document level Data and Item level data

Hi,
Can anyone please explain the difference between Document level data and Item level data for sales order.
Thanks
shalini

Item is the lowest level detail of the order. For ex it would be a particular material. Document would be the overall "top" level. Usually refered to as header level. It relates to everything in the document.
pts appreciated

Modification date for Sales Order

Hi Guys,
Is there any field like Modification Number for SalesOrder. then where can i find this. thanks in advance.
Thanks
Kiran.B

hi,
once we create a sales order, any changes made can be seen in tables,
CDHDR - sales doc. header data
CDPOS - sales doc. item data
you can use the info from these fields if trying to develop some logic regarding the changes.
Pl reward if it helps.
Thanks,
Sadhu Kishore

Header Level Data In Sales Doc

Similar Messages

Maybe you are looking for