Billing Output (Customer Hierarchy)

Hello Guru's
I have a requirement to setup output for billing documents via ale. Business needs this only for speciality customers which they have done via customer hierachy (c) in customer master under sales area tab.
I have below mentioned questions on the same.
1) Based on customer hierachy, do I use account group or put the output to billing documents?
2) Do I determine output type and everything first or setup the partner profile for idoc first and then follow with output procedure?
3) Which transmission medium shall I use for the billing output it will be sent via email by day end batch job, I am thinking of using tranmission 6 for edi let me know, if I am correct.
Thanks
Aman
Edited by: amansgh on Oct 10, 2011 12:48 PM

Hi
customer hierachy and node is basically for reporting and statics purposes.
if you divede customers whole salers and retailers in that again if you maintain hierachy node north customer South customers or export customers. based on this if you would have maintan the condition technic and conditin recor d.when generate the report it will give the report based on selection creteria.
for path you see SPRO SD Master Data Busineess partneer - customer -Customer hierachy define hierachy type.
I hope you have understood.
Thanks Regards
.Surya
Edited by: ramakrishna suryanarayanarao on Sep 15, 2008 3:15 PM

Similar Messages

Billing Output Access Sequence

We have the following requirement for output determination and I was wondering if anyone has configured the following, bearing in mind that some required fields do not exist in KOMB
1 - Sales Org/ Customer Hierarchy
2 - Sales Org/ Sales Doc Type/ Sales Doc Number - (pricing agreement number)
The idea is that the client wants to be able to send a specific variant of the invoice to a customer based on a combination of the above criteria.
Any thoughts as to if there is an existing condition table that I can use, or do I have to create a new one. If so, what are the steps to get the non-standard delivery fields into my condition table?
Thanks,
Kevin Webb
SAP Senior Consultant
Innovapost

Thanks for your response.
I am trying to ascertain which structure best suits my needs, and if it is even possible to include KNVH-HKUNNR.
I was thinking of using structure KOMKBZ5 (Billing document header) with USEREXIT_KOMKBV3_FILL, but am concerned that the link would not be made between the payer and the hierarchy customer when finally generating the condition record.
Any thoughts?
Thanks again!
Kevin

Customer hierarchy-Discount not flowing through

I am facing problem in customer hierarchy in pricing.
I have assigned account group 0012 to 001 all customer. 0012 is Main company who is not issuing orders. I think this may be due to Partner determination settings. However, I have set 3 levels 1D mai n office which is not issuing sales orders act group 0012 Set partner determination at customer master level and sales document header TA. In sales order in Partners tab I am getting 1D but not getting other like 1C nor 1B nor 1A.
Assigned sales area as well to hiegher level sales area, order type to "A" cust. hierarchy, VDH1N well maitnined 0012 act grp to lower level 2 company which both are 001 act group.
In VK11 maintained HI01 % discount different for head office & two branch office with same sales org, Distr Channel and division.
Here HO is given 2% discount and one branch office 5% and another 7%
When I am creating sales order for 7% branch, in pricing procedure it shows only 2% (HO) discount but not 7% for branch office. I have also tick marked in XD02 at billing tab price determination. In pricing analysis hirearchy 02 is having Exclaimation in Customer field. So why I am missing this customer field even though I have maintained that customer in VK11. Hope I have summarized all details. If any questions please feel free.
I shall appreciate if you know the resolution.

This is now resolved by proper settings in Customer Hierarchy

Customer Hierarchy not showing in sales document

Hi All,
I have used the standard hierarchy type (A) to create a 2(or 3) level hierarchy (top level node, 2nd level node and sold t party) and the hierarchy assignments look fine at the customer level. I have assigned the hierarchy type to the sales order type as well. But the hierarchy does not get carried over to the sales orders (contracts) when I create the documents. I am sure it is something really silly, but any idea what I might be missing or where to start looking.
Thank you so much for your help in advance...
Shubha Tandon
[email protected]

Have you Mainted Price determination in the custome masrter record of the billing Tab.
Have you correctly maintained the partner determinatin procedures.
Have you assigned Customer hierarchy to your sales area
Have you created Customer with 0012 Account group.
Now you need to assign the customer creatd using 0012 to the customer 0001 account group.
Have you maintainted the Customer heirarchy in VDH1n transaction..
Here you need to assign 0001 account group customer to 0012 customer
If u have maintained all these settings correctly you will get the hierarchy customer in SO.

Need info on Billing Outputs

Hello,
I need info abt billing Outputs - The language is maintained in Bill to party (Customer master), Its maintained in Condition record, It can be changed while creating the invoice.
Now my question is, which of the above three cases has got highest priority.
Could some one provide me some info on this?
Regards,
Krishna

By default, we will maintain language in Bill-to-Party & also Condition record. But if required, it can be chaged at Invoicing level while taking output. Priority will be Bill-to-party, followed by Condition Record.
Regards,
Rajesh Banka

EDI billing outputs are capturing credit memos as well as invoices

I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator. Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices. I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices.
The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard). Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing? I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word.
How can I display/change Application V3, in order to check itu2019s contents?
Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
Thank you in advance for your assistance.
Application V3 (what specifies what transaction type this pulls?)
Message Type ZURH,
Process Code SD09.
Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
Transmission Medium is 6 EDI.
The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.

Satish,
Thanks for the suggestions.
I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer linked to ZURH, as I would expect (5010013645     BEST BUY CANADA Vendor #41448     PY          6     1).
I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place. I donu2019t find entries under any other key combination. How would I check if Output Condition records are maintained for credit memos?
In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either.
In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
10     1     RD00     Invoice
20     2     ZPRO     Proforma Invoice
30     1     ZCAN     Canadian Cust. Inv
40     1     ZCOM     Commercial Invoice
50     1     ZDN0     Debit Note
60     1     ZCN0     Credit Note
How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing?

Customer Hierarchy details in SAP ERP BP transaction

Dear All,
Currently we are using BP transaction in SAP ERP and also using customer hierarchy transaction VDH1N.
Now the problem is we cannot see customer hierarchy in BP transaction, we have any option that we can create relationship in the BP transaction, however its a double effort. Is there any option that we can see the Customer Hierarchy details in SAP ERP BP transaction?
Regards,
Murali

Hello Murali,
With BP transaction, do you mean business partners in XD03 / VD03?
>> we cannot see customer hierarchy in BP transaction
No, you can't see the customer hierarchy in XD03. That's correct.
In XD03 you have sold-to, payers, bill-to and ship-to.
You also have hierarchy nodes (012).
In my opinion, the customer hierarchy should only have relations between hierarchy nodes and sold-to(s).
Therefore these are different information segments => No need to see the hierarchy from the BP transaction.
Hint: Maybe that is the reason why the functionality is not available in the standard system!

Send the billing output by e-mail for the user

Hi,
Can you tell me if it's possible to send the billing output by e-mail (Medium = 5 - External send) for the user that create the billing document? the e-mail of the user is in SU01D.
Thanks in advance
Dora

Hi Dora,
What you can do is when you want to send a mail to customer after you receive the email for bill is do the following settings.
1) Create a condition record VV31 with the required Key combination where you can give the name of the Employee or end user with the email id.
2) Select the trasmission medium as 7 ( Simple Mail)
3) Once the Billing is done E-Mail will be triggered.
4) Downlaod it or forward it to your client with the additional text in the E-Mail.
Hope this helps.
Thanks and Regards
Rohit Dujari

Triggering billing output for multiple emails

Hi Experts,
We have a scenario wherein a single billing document output gets triggered for multiple emails. The requirement is to send the invoice layout copy to multiple emails where we maintain customer mail ids in customer master record.
When tried ,we found option in customer master record and maintained multiple email ids to send the billing output.The system has considered first email id from customer master record and did not consider next mail ids from CMR. Could you please suggest now how can we suffice this requirement .
Thanks in advance.
KV

Dear Kv rekha,
Check whether the following thread helps you.
http://wiki.sdn.sap.com/wiki/display/Snippets/Howtosendmailtoadistributionlistoragroup+ID
Thanks & Regards,
Hegal K Charles

COPA - Customer Hierarchy

Hi All,
I need to have Customer Hierarchy as my Characteristic. Could any one guide me how to crate it.
Thanks
Praveen

Hi
1. You create a Cust hie in SD and you maintain a derivation rule in COPA...
2. While you create derivation rule, how many Cust Hie levels are you able to see in Source and Target Fields?? In Std system, the same is a 3 level Hier... Hence, KEDR shows 3 Levels of Hier
3. If KEDR is not showing 6 levels of Hier, then you should go and refresh your COPA data structure in KEA0 and include the new hier levels in your data structure
4. The process is - You map a customer to the Cust Hie in the master data or whereever in SD... At every billing, the Hie Levels would be updated to COPA.... The no of levels that would be updated to COPA depends on your der rule in KEDR i.e. it depends on how many levels are you able to see in KEDR derivation step
5. If the 6 hie levels are visible in KEDR, you dont need to maintain any char values in KES1
Regards
Ajay M

Customer Hierarchy in Pricing

Hello,
Please tell me how Customer Hierarchy is used in Pricing? Concept?
What are the config. we have to do?
How do we track it in the pricing?
Thank you.

dear emre
Customer Hierarchies
Use
With customer hierarchies you can now create flexible hierarchies to reflect the structure of customer organizations. For example, if your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, you can create hierarchies to reflect the structure of these groups. You use customer hierarchies in order and billing document processing for partner and pricing determination (including rebate determination) and for creating statistics.
You can use customer hierarchies to assign price conditions and rebate agreements to one of the customers subordinate levels, to ensure that all subordinate levels are valid for the customer. For each node that you indicate as relevant for pricing, you can create condition records for pricing. If one or more nodes in a hierarchy path for a sales order contain pricing data, this is automatically taken into account in pricing.
Integration
You can also use customer hierarchies for evaluations in profitability analysis (CO-PA) and in the Sales Information System (SIS):
To evaluate customer hierarchies with the sales information system and in the profitability analysis, you can maintain the field Hierarchy assignment on the Marketing tab page in the customer master record for a hierarchy customer. Here you can maintain 10 features for hierarchy customers (HIEZU01 to HIEZU10). You can use these to evaluate hierarchies statistically with up to 10 levels. (Field catalogue VHIE)
Note that the hierarchy assignment is statistical. If you change the customer hierarchy, you may need to change the hierarchy level manually in the customer master record in the Hierarchy assignment field.
Features
A customer hierarchy is a flexible structure consisting of customers. Each customer - with the exception of the uppermost customer - refers to another customer at a higher level in the hierarchy (known as a higher-level customer). Customers that are assigned to higher-level customers are known as dependent customers.
To be able to display organizational elements, that are not independent partners, you can assign pure hierarchy nodes (account group 0012) in the hierarchy. Specific data can be assigned to a hierarchy node (for example, address, price conditions, rebate agreements) and this then applies to all subordinate customers.
As all nodes in a hierarchy are time-dependent, you can adapt the customer hierarchy to changes in the structure of a customer at any time.
Customers can be reassigned in a hierarchy When reassigning a customer, all subordinate customers are moved with it
You can add new customers to a hierarchy When you assign a new customer to an existing hierarchy, all pricing data, that applies to the higher-level hierarchy node, is automatically copied from the customer
You can also remove customers from the hierarchy
you can refer http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f4d9545a11d1a7020000e829fd11/frameset.htm
rewards if it helps
siva

Rebate agreement with customer hierarchy

Hi,
I want to use customer hierarchy for customer rebates where in the accrual rate with scales shall be maintained only the high level customer. Invoice values of all the subordinate customers should e accrued using this rebate agreement.
Have learnt about extended rebate agreement functionality wherein such a scenario can be adopted.
Looking for a solution immediately to meet the week end deadline for POC.
Regards,
Rajesh Mohapatra

Thanks Veera !!
In this case my rebate receiptant is one only.
I am trying to use a customer hierarchy node (scaled down customer code w/o partners, recon account etc.) and made it relevant for Rebates & Price determination.
All the customers in the hierarchy are also relevant for Rebates.
But the condition record maintained with hierarchy node is not getting picked up the billing document as system is looking for the subordinate payer instead of the hierarchy node.
Not using the same node as Rebate Receiptant. Incase of using wrt the below link, am getting error as "Customer for function PY may not have account group 0012".
Ref : http://help.sap.com/saphelp_ides/helpdata/en/5d/363ec3583f11d2a5b70060087d1f3b/content.htm
Regards,
Rajesh Mohapatra

Billing output error

Hi Friends,
In one of my billing output i am getting wrong country name printed( example instead of IRELAND .....i am getting IRLAND)
I have checked customer master data and the partners functions assigned to customer( there the preview is coming correct). During the output I am getting above error.
Do we have any remedy for this.
Thanks in advance.

Hi,
Please check whether it was fetched from the CUSTOMER TABLES or From the Text
I think it was maintained as Text.
Please check the Smartform for the Text and correct
If you have to the smartform you can change the Name
For technical details on Print program and the SMARTFORM
Goto the Nace with the Application V3 and in the processing routines you can find the PRINT PROGRAMS & SMARTFORMS
Please revert back if you need more details
regards,
santosh

Billing output through email

Hello SDNs,
I have a requirement to send the billing output directly to the customer(BP) who is receiving billing document but it should be specific customers. Can you please explain where do we maintain for automatic billing output through customer email.
I have maintained transmission medium as email at billing output type level and maintained output codition record level.
Outout is not triggering as i have maintained above settings. Can you please guide the steps for getting output through email.
Regards,
K

Hi,
If you want to sent email to the BP the invoice copy then create your output type in SPRO>SD>Basic Functions>O/P control>O/P determination>O/P determination using condition technique>maintain Output Determination for billing documents.
Select RD00 and create an output type of your own. In the Default values tab maintain transmission medium "5" and partner function "BP" and Communication Strategy "CS01". Now at left side "Dialog structure " Maintain the values for each one
In the processing routines maintain medium "5" .Your program ,form routine and form.Also type "2 PDF".
In partner functions Maintain medium "5" and partner function "BP" these are the configurations when you maintain the new output type.
After creating the new output type maintain the same in output determination procedure. with Step/Output type (created by you).
Maintain the email address in customer master of BP.
Also check in SCOT to ensure the email is triggered

Customer Hierarchy and product Hierarchy

Hi friends what is customer Hierarchy and what is product hierarchy?
please explain step by step with examples.
mail id: [email protected]
Thanx.

Hi Sirivas,
CUSTOMER HIERARCHY:
Customer hierarchies are available in Sales and Distribution, so that you can create flexible hierarchies to reflect the structure of customer organizations. If your customer base includes multi-level buying groups, cooperatives, or chains of retail outlets, for example, you can create hierarchies to reflect the structure of these groups. Use customer hierarchies during sales order processing and billing for determining pricing and running statistics.
 A customer hierarchy consists of nodes.
 To create a customer hierarchy:
1. Create master records for each node.
2. Assign the nodes to each other.
3. Assign the customer master records to the relevant nodes.
 Hierarchy nodes are only valid for a certain period of time. They may also be moved. If a node is moved, the system automatically reassigns all related nodes and customer master records.
With customer hierarchies, you can assign price or rebate agreements to a higher level node. The agreements are then valid for customers at all subordinate levels to this node. You can create pricing condition records for each node indicated as relevant for pricing. If one or more nodes in the hierarchy path of a sales order contain pricing information, the system takes them into account automatically during pricing.
'How to check'
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
All the customizing is in SD/Master Data/Business Partner/Customers/Customers hierarchy
1) Define hierarchy type: just put and ID and a name to the new hierarchy.
2) Set partner determination: if you want to user the hierarchy in price determination, then, in the orders, at the header level, you have to have a Partner Procedure with a partner function for each level. In the partner procedure, in each partner function you must indicate the source partner function. With this information, in the order, you obtain the business partner for each partner function.
3) Assign account groups: you indicate which accounts groups are allowed for being part or your hierarchy.
4) Assign sales areas: simple you indicate which sales areas are allowed in your hierarchy. (Here you can customize common sales areas, just for not having to build de hierarchy in all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documents uses hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for example you create a condition discount for a customer that is part of such a hierarchy structure. All subnodes in the hierarchy below that customer, will thus receive the same discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function - but you don't need that right?
Next assign your customer account group to the hierarchy type. And enter the combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners - customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and you agree both on a discount. Unilever does have different locations / businesses and you have to maintain the discount for all customers. If you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this way it will be valid for all customers in the hierarchy.
Product Hierarchy:
The product hierarchy on the Basic Data screen is used to depict the competitive materials of competitor 1 in relation to those of competitor 2. Here, your own company and its materials are also regarded as a competitor and as competitive materials respectively. You can use this representation as a basis for market analyses.
Normally we enter competitive materials using material type WETT. When entering your own materials as competitive materials, you can, however, display the product hierarchy on the Basic Data screen for other material types too.
Requirement type determination is based on the "Origin of requirement type in requirement type determination"
In this field you can select an alternative search strategy (source):
Source 0 = Material master strategy, then item category and MRP type
Source 1 = Item type and MRP type strategy
Source 2 = Item type and MRP type strategy (as for source 1) with additional check of the allowed requirements type
e.g. If you set value "0" system will first strategy group in material master based on that it will determine requirement type and no value found then it will determine requirement type based on item category and MRP type.
Above settings can be found at SD --> Basic Functions --> Availability Check and transfer of requirement --> Transfer of Requirement --> Determination of Requirement type using Transaction
For make to order std strategy group 20 is used to which req type KE is assigned.
Check
Check in Tcode OVZH, what requirement class is assigned to your requirement type
Check in Tcode OVZG, what value is assigned to field "Consumption" in requirement class because that determines consumption posting.
The product hierarchy is used to group materials by combining different features. It is used for analyses and pricing. A product hierarchy can consist of up to Eighteen characters. Its features can be combined in various ways.
Example: A dishwasher can be described by product hierarchy 000010000200000002. This series of characters states that dishwashers belong to the category electrical appliances (series of characters 00001, position 1-5), and also to wet appliances (series of characters 00002, position 6-10) and, finally, to dishwashers (series of characters 00000002, position 11-18).
One can maintain the product hierarchy via transaction "OVSV" and "V/76.
Path = IMG-Logistics General-Material master-Setting for Key fields-Data relevant to SD-Define Product hierarchy.
The product hierarchy is maintained in the Basic Data view of the material master record, and is used for evaluation as well as price determination in materials management.
The standard SAP allows only 3 levels, but you can go up to 6 levels, for additional 3 levels u will have to take abapper help and add 3 more fields and corresponding data element into structure. So that in material master drop down you will see 6 levels.
The transaction which will be useful to change product hierarchies for material master will be V/76.
Yes, You can print the levels of the product hierarchy through a report.
Use the view SE16 - V_T179 (Table Name) to display Product hierarchy with level numbers.
Field Name is PRODH
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Billing Output (Customer Hierarchy)

Similar Messages

Maybe you are looking for