Payment Terms(Different at header and Item)

Hi,
While creating an order with two line items having different materials, A different payment term is picking for one material at item level which is different from header.
Where as for other material same payment term is coming at both header and item level.
Could please let me know where do we maintain entry to pick a payment term which comes at item level.

Mohan Hi,
Please also not that SAP Standard set the same payment term at the header and the item level. As mentioned, the payment term default value at the sales order comes from the customer master data.
Best regards.
Ido

Similar Messages

Different division at header and item level in Order

Hi Gurus,
i am facing this issue where while creating quotation in CRM i entered sold to party, selected the org data ( OA/DI/OP ). i entered the product with quantity. now at item level in Organization tab my sales area is showing as ( OA/DI/01). system is picking the division maintained for product which is 01) so division is different at header and item level. i need the header division to be used at item level as well.
how can i achieve this?
Thanks and Regards
Sudhir Grover

Hi Sudhir,
Make sure the settings in the SPRO>CRM>Master Data>Products>Special Settings for Sales Operations--> Define Division settings is activated with Header Div. Act.
Also check the details in the IMG activity documentation for define division settings.
Hope this helps.
Regards,
Chandrakant

Different payment term at header and item level

Hi,
In sales order(VA03) we r getting different payment term for header and item.
Eg: For header we get MZ30 and for item level MZ60.
It's only for a particular material. I have been asked to find out why? Any thoughts?
Thanks in advance
Chesat

Hi Lakshmi,
Where do we maintain this entry to reflect this change.

User Exit to make Payment Term field non editable in item level .

Hi all,
User wants to make the Payment Term field in sales order as non editable and Payment terms is copied from Customer Master to Sales order.
I use user exit MV45AFZZ (USEREXIT_FIELD_MODIFICATION) to make Payment Term field non editable in header level.
I am not able to do it in item level. Pl help to to make Payment Term field non editable in item level.
Thanks,
sunil

Hi,
You can try implicit enhancement in the include MV45AF0T_TCTRL_U_ERF_AUFTRAG_I
use below code.
DATA: WA_COLS LIKE LINE OF TCTRL_U_ERF_AUFTRAG-COLS.
   LOOP AT   TCTRL_U_ERF_AUFTRAG-COLS INTO WA_COLS.
   IF WA_COLS-SCREEN-NAME = 'VBAP-ZTERM'. " Check the field name
   WA_COLS-SCREEN-INPUT = 0.
   WA_COLS-SCREEN-OUTPUT = 1.
MODIFY TCTRL_U_ERF_AUFTRAG-COLS FROM WA_COLS.
   ENDIF.
ENDLOOP.
It better to control it via a custom authorization object.
put a authorization create a custom authorization object so that you can restrict it for a certain users.
AUTHORITY-CHECK OBJECT 'ZTERM'
         ID 'ACTVT' FIELD '02'.
IF SY-SUBRC NE 0.
   LOOP AT   TCTRL_U_ERF_AUFTRAG-COLS INTO WA_COLS.
ENDLOOP.
ENDIF.
Regards
Aromal

Partners in Header and Item level

Hi,
I am creating a credit memo through the following steps.
1. Create rebate agreement in VBO1.
2. Create sales order in VA01.
3. Release through VKM4.
4. Create delivery through VL01n.
5. Post goods issue.
6. Create billing document through VF01.
7. Update billing doc through VBOF.
8. Settle rebate agreement through VB(7.
When the credit memo is created,in debugging mode(VB(7),if I change the partner for "header", partner for "item" is also getting changed.This is as per my requirement. But I wanted to know whether there can be a case where item partners are different than header partners. (Right now I am having only one line item in credit memo.I am not being able to create a credit memo with more line items by repeating all the steps above).

Sowrabha
It is possible to have different Partners for Header and Items... However, in your scenario it doesn't create any problem, as it all depends on the Partner Determination Procedures in the customising....
Thanks
Amol Lohade

Delivery tolerance at header and item level in sales order

Dear All,
My client wants to maintain delivery tolerance at both header and item level. NOTE: The tolerance at sales order header is different than the delivery tolerance at sales order item.
eg if i maintain 3% plus and minus tolerance at item, the header level tolerance can be 2%.
Also if there are more than 1 line items, the system should give warning message, when it finds that the delivery tolerance at item level can be maintained but that of the header level cannot be maintained and vice varsa.
Awaiting an early help and thankful for the same in advance.
Regards,
Avnesh Kamdar

Hi Avnesh,
Delivery tolerance can be made in the customer master,sales org data ---delivery tab.
Delivery tolerance is always at item level.
Reward points if it helps.
Regards
Karan

Payment terms different between sales docs

Hi Gurus.
Why do I have payment terms different between sales doc and billing doc for the same customer?
Detail: the sd and company code vision has the same value in customer master data (xd03, vd03).
Thanks in advance!
Renato

Dear Renato
Go to VA02, input the sale order and execute. There click on Environment from top menu bar followed by changes. You would find four options to choose. Select
- Additional info and
- Time of Change
This would give you who have changed the datas related to that sale order.
thanks
G. Lakshmipathi

Sender FILE Adapater Content Conversion: Header and Item Data

Hi
I need to pick a file and do the content conversion. The XML structure which should be formed should be in the below format. I have a CSV file which needs to be converted.
Kindly suggest how can I maintain parameters for Header and Item level data in Recordset structure.
How can I specify in Recordset parameter which is Header(Customerno, Doc type and Address) and Item level(Line Item) data.
<?xml version="1.0" encoding="UTF-8" ?>
<customernumber></customernumber>
<documenttype></documenttype>
- <Address>
        <name1></name1>
        <name2></name2>
</Address>
- <LineItem>
        <material>100016</material>
        <amount>1000</amount>
</LineItem>

Hi Swetank,
The file after conversion should have one Header and you can have any number of line items.
Once you choose File Content Conversion in the message protocol header while configuring the Sender File Adapter, you get the following enteries in the Content Conversion Parameters:
Document Name
Document Namespace
Document Offset
Recordset Name
Recordset Namespace
Recordset Structure
Recordsets per Message
Key Field Name
To maintain the Header information, Some entries are mandatory, i.e.
Recordset Name: Here please specify the name of the structure. It is included in the XML schema.
Recorset Structure: Here you need to enter the sequence and the number of substructures. Since Header is one but you can have many Line items, you will write:
customernumber,1,documenttype,1,Address,1,LineItem,*
this format is clearly explained in the link provided by Divya.
And in the Additional fields you need to write the name of fields corresponding to different Recorset Structures and also add some property to it, like fixed lengths, use some separators etc.
and Most important field is:
Key Field Name: If you specified a variable number of substructures for Recordset Structure, in other words, at least one substructure has the value *, then the substructures must be identified by the parser from their content. This means that a key field must be set with different constants for the substructures. In this case, you must specify a key field and the field name must occur in all substructures.
Here you need to enter LineItem as it is the only Recordset Structure with an *.
I hope this solves your problem,
Thanks and Regards,
Varun Joshi

How can we revise the pricing both at header and item level of sales order?

Dear All,
Now there's one issue of the pricing to me. i want to revise the pricing both at header and item level of sales order. but after i finished the cutomize and tested it, it's more different as i thought. i found that the pricing can revise at the one side only,for example, if i revise the pricing at item level and it's grey and can't be revised at the header. on the other hand, it's the same result what's happened at item.
So, in my opinion, we can't revise the pricing both at header and item, right? if not, please give me more advices and teach me how to solve the problem. thanks a lot.

Dear Lakshmipathi,
Thanks a lot for your kindly and useful answer for me and I learn more for the pricing technology.
I didn't notice the way that you reminded ago therefore I also saw the button at the condition tab. And your suggestion makes me know more.
And I had tested the way that you said, I met with a question. Below is my opinion for my testing.
I had created one SO and the pricing was $10, then I revised the pricing from 10 to 15 by VK11. It can't be updated automatically at SO and I must update it manually by clicking the "Update" button. This is OK for my testing, but I have another question to disturb you for the use of "Active" button. When I click the button and nothing is responsed, it's quite different what you said. So, please give more detail for the Active button. Thanks a lot.

Header and Item Conditions in EBP PO

HI All,
I've just checked the pricing conditions in spro of SRM and as per my business requirement I need to maintain both header and item conditions and replicate the values back to r/3 in extended classic scenario like freight,surcharge,discounts e.t.c, with this functionality can we meet the requirement or any additional settings required,kindly advice me.
Thanks and Regards,
Sathya kumar.

Hi,
Header conditions in PO does not exist !
You will have to develop it.
Then you will have to use ECS BBP_ECS_PO_OUT_BADI for modifying the data you send to ECC PO in order to not send the whole price calculated into SRM but dispatch on one side the price before condition and on the other side the different condition type.
The goal is that R/3 should be able to recalculate the final price based on the condition types you entered in SRM.
Kind regards,
Yann

Header and Item conditions in MIRO

Hi All,
There is a PO created with Import conditions .We have given some conditions in Header level (AED) and some conditions in Item level (Customs duty like SED..etc). We maintaind the vendor (customs-ABCD Vendor) in header conditions as well as Item level conditions.
As per the process, we are trying to create the Customs invoice(MIRO) for the PO.This vendor(ABCD Vendor) is FI vendor . While doing MIRO , same Vendor name is appearing two times for selection ."One" is for Item level Conditions and "another one" is for Header level conditions.
We can select only one vendor, either Item level vendor or Header level vendor . If I select "one" vendor , it will give the item level conditions only..(Here vendor is same for Item and Header level).We can only select and process Item level conditions for that vendor.
If I select "another one" vendor , it will give the header level conditions only..(Here vendor is same for Item and Header level).We can only select and process header level conditions for that vendor.
Is there any setting to be done to appear the header and item level conditions at a time in MIRO Vendor (if Vendor is same ) in commercial Invoice ?
Please provide SAP behaviour on these kind of scenerio...
Thanks

Hi,
Header conditions in PO does not exist !
You will have to develop it.
Then you will have to use ECS BBP_ECS_PO_OUT_BADI for modifying the data you send to ECC PO in order to not send the whole price calculated into SRM but dispatch on one side the price before condition and on the other side the different condition type.
The goal is that R/3 should be able to recalculate the final price based on the condition types you entered in SRM.
Kind regards,
Yann

Payment term Field at header level

Hello
my requirment is while creating sale order the payment term field at header level should be in display mode. or not shown while creating sale order. doesnot want to maintain user exit. or anyone have knowledge of field (of payment term ZTERM ) object ?
Regards

Dear Mr. M Yasir Dogar,
To this requirement as Lakhsmi says, to make the Payment term in display mode, without user exit you can do with Tansaction variant SHD0. It actually make a view sort of control.
Steps:
Run T CODE: SHD0
Transaction VA01
Variant ZVA01_VARIANT
create a sales order.
during the process system, records all the details of object involved in the sales order creation.
and it records with the screen number as variant name.
After execution go to details, Go to
Name of screen variant: ZVA01_VARIANT_4440
and in Payment terms VBKD-ZTERM, select Output only (means it will only display the data from master) and others option also will be there like * Invisible, Required.*
Select the appropriate one.
Along with this activity,in the authorization - profile the Variant should be assign to the USERS having T CODE : VA01. This can be done by the Basis team.
We did similar to control the manual entry of Payment terms.
Regards,
Mani

FCC parameters for header and item

Dear All,
I am working on a File to RFC scenario. The file has the PO deatils from which Salesorder has to be created in R/3. Am using the BAPI BAPI_SALESORDER_CREATEFROMDAT1 to create salesorders. I have tested the scenario with XML message - it is working file .
The problem is with FCC.
The structure of the file is as follows
PO number,podate,deliv. date,cust. material,quantity,receiving point
message type:
-->MT_messagetype
>input
>header
                po number
                po date
                deliv date
>item
>item
                     cust_material
                     quantity
                     receiving point
>partner
>partner
                     dummy field.
input is the recordset
i have to get the first 3 fields from the file inlto header and the rest into item.
i have created a dummy field in partner because I am mapping a constant value to sold to party in partner node .
what should be the FCC parameters ?

After looking at your structure which is comma separated and doesn't have any keyfields it will be difficult to content convert it into different nodes like header and item.
I was looking at using fixed field lenght's along with field separator to split the structure, as the first 4-5 fields of u r row seem to be standard structures which will have fixed length, but then your last field "receiving point" is not a of fixed length.
so as long as my understanding goes you will have to content convert the input into a flat xml structure like this:
<input>
          <header>
              </po number>
              </po date>
              </deliv date>
              </cust_material>
              </quantity>
              </receiving point>
        </header>
<input>
Recordset name - input
Recordset structure --header,*
FCC
header.fieldNames -- po_number,1,po_date,1,deliv_date,1,cust_material,1,quantity,1,receivingpoint,1
header.fieldSeparator -- ','
header.endSeparator -- 'nl'
Since in your scenario looks like you are creating one sales order per row of file, the above structure should do the job for you.
Cheer's

BAPI_SALESORDER_CREATEFROMDAT2, Header and Item Level Ship-to

I have a situation where I want to have different header and item level ship-to accounts on a sales order. When I use the BAPI_SALESORDER_CREATEFROMDAT2 to create the order by passing the Ship-to for header and Item in order_partners table, the header ship-to is not updated.
This works fine if the header and item level ship-to are same.
Any ideas.

Hi Amit,
put a breakpoint at the BAPI and check your PARTNERS table
e.g. in the case, i am using iterms partner for line 10 & 20 that is different to the header table (000000)
         PARTN_ROLE PARTN_NUMB ITM_NUMBER TITLE           NAME
    1     AG        |EDICUS         |000000    |               |                         <
    2     WE        |DODGE         |000000    |               |                         <
    3     WE        |EDICUS         |000010    |               |                         <
    4     WE        |RWCUS         |000020    |               |                         <
if your table is not like this , it won't work
otherwise, post the relevant code and we can check
kind regards
Paul Quinn

Header and item level approval using N level BADI

Hi Experts,
I beleive we can use either header level or item level approval workflow (WS14000133 and WS14500015) using N Approval-BADI. Please advise what information approval will be able to see if we will be using WS14000133 (Header level approval). Can he see all line item information or header level only.
Regards,
Kamal

In SRM the same BADI is used for SC, PO, Invoice and others as well.. If you see the example implementation provided by SAP, you can see the use of CASE statement with different Business Objects and code under it.
Irrespective of the Header level or Item level approval workflow the same BADI has to be implemented.
The difference between Header and Item Level approval is
1) In Header level, approval or rejection is done for the whole cart (there can be 1 item or multiple items).
Approver will be able to see all the items in the cart.
2) In Item level, approval or rejection is done for each and every line item. here is an example ---
Line item 1 has Cost Center as Account Assignment Category and has to be approved by Users A and B.
Line item 2 has Internal Order as Account Assignment Category and has to be approved by Users C and D.
Item 1 goes to user A and once approved, it goes to B. they will not be able to approve or reject item 2. but we can restrict user A and B to see item 2 or not by setting a flag..
Item 2 goes to user C and once approved, it goes to D. they will not be able to approve or reject item 1. but we can restrict user C and D to see item 1 or not by setting a flag..
The SC will get released only after all the items are approved.
For Header Level approval, you need to fill the APPROVAL_TABLE.
For Item Level approval, you need to make use of APPROVAL_TABLE, ITEM_APPROVAL_TABLE and ITEM_APPROVAL_OBJ.
Examples provided by SAP might give you an idea how to code for Header and Item Level.
Hope this gives you some information .....
Regards,
PR.
Edited by: PR on Nov 25, 2008 10:50 PM

Payment Terms(Different at header and Item)

Similar Messages

Maybe you are looking for