Billing Category
Dear SAP Experts !
The Billing Category In the VOFA in Billing Type (FI : ZZUL alis)
Item Category TAD service.
When I am viewing the Options of Billing Category there is only 3 entries : P ,U, W .
Where as in the Database Tables I find All entries A , B, L. etc entries.
My requirement I want to Put A order related billing for the billing type but system prompts enter a valid value.
Because in the VFX3 I find the order related billing is having document category L which is Delivery related billing.
How to Change the Billing category from L to A (order related billing).
regards,
A S
First I would like to clarify on your comments
Because in the VFX3 I find the order related billing is
having document category L which is Delivery related billing
What you are seeing in VFX3 is based on your order type and not billing type. In VOV8, for your order type, you can see a field "SD document categ".
For standard order types like BV, OR, this would be C, whereas for DR (Debit Memo Request), this would be L.
Now I would like to clarify on your another comments
When I press F4 there I can See Only Three Entries
IS this Standard.
Yes it is a standard.
thanks
G. Lakshmipathi
Similar Messages
-
Modify Task Billing Category Project Server 2010
Dears , I am filling a new timesheets, it already contains tasks from projects. can I change the billling category for these tasks?
the billing category is disabled for them.
any ideas?
Twitter : @MShoubaki | http://jo.linkedin.com/in/mshoubakiMohammad,
I just came across your question. The billing category is an attribute of a timesheet line, which by default are standard. You can have multiple timesheet lines per assignment. In order to enter time in a non-standard billing category,
you will need to manually add the line to the timesheet, and at that time, specify the billing category to use. The following article has additional details.
http://blogs.msdn.com/b/project/archive/2008/05/20/timesheet-classifications.aspx
I hope this helps.
Best regards,
Justin
Justin Naughton -
What are billing category and SD doc category?
Hi,
what are SD document category, billing category and biling types and how are they related to each other?
which transaction can be used to set them?
ThanksHi
Billing category (used in a billing type)
Used to differentiate the billing documents by requirements for:
u2022 invoice printing (selection criterion)
u2022 billing document creation (selection criterion)
u2022 forwarding to Financial Accounting
SD document category (used in a billing type and also in order type)
A classification for the different types of documents that you can process in the sales and distribution system (for example: quotations, sales orders, deliveries, and invoices).
Use
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
Unfortunately you cannot create more keys for both of these it is all predefined and given in the standard
Billing type is different kinds of billing document types like F1 ,F2 , F5 ,BV and FAZ etc
these can be defined in t code VOFA
Regards
Raja -
Order related billing for item category
Hi Gurus,
Can you please suggest what option should I choose in Billing category for making it relevant for billing. ex c,f,g etc
It is the item for return and be used in credit memo with order related billing.
So flow is like this-
Return Order-Return Delivery-Credit Memo.
Thanks
BawaHi there,
You should make order related billing only (here it means return order related).
Since you already determine a pricing proc for your returns, it will adopt the same billing.
Regards,
Sivanand -
Excise Invoice for Order Based Billing Scenerion
Dear Friends,
We have a scenarion, wherein we are working with Sales Order Based Billing.
We are in the process of Implementing CIN with TAXINN.
Is it possible to create excise invoice for the scenarion of Sales Order based billing, instead of delivery based billing.
If yes, what are the steps we need to follow to configure the same.
Regards,
Harshhi
If u want the create Excise Invoice for Order Based Billing Scenerion, u must be set in billing document in General control in fields is.
<b> SD document categ. M Invoice
Transaction group 7 Billing documents
Billing category
Document type
Negative posting No negative posting
Branch/Head office Customer=Payer/Branch=sold-to party
No
Invoice list type LR Invoice List
Rebate settlement
Standard text </b>
Best copy of F2 Invice. and this billing type in outgoing invoices in Tax on goods movement in Logistics general.
Rewards point it helps -
In support of a consulting company using timesheet custom billing categories to designate project time as billable onsite, billable offsite, and non-billable, I've encountered a series of issues which appear to be associated with the custom billing category
timesheet lines. These issues cause timesheet users to get frustrated, and contribute to misalignment between project actuals and timesheet actuals. We're in Single Entry Mode, no pre-population, SP1 and April 2014 CU Installed.
I'll enumerate the issues here and pose the question to the community as to whether others are experiencing any/all of these things, and if so, ask if any workarounds have been discovered. We're working with Microsoft to validate these independently,
but I am posing the questions to the community to gather additional information, and hopefully save some folks time in troubleshooting similar issues.
1.When time is entered on an assignment into timesheet lines of multiple billing categories, only time entered since the last save is getting saved and ultimately sent, on timesheet submit, to the approval center. Although the previously entered and
saved time appears in the application interface when the timesheet is re-opened, only data since last save is actually saving to the server or processing through the approval center. We believe this is the primary cause for timesheet and project actuals
being out of alignment.
2."_ Error Loading". When assignments are added, deleted, or changed after a timesheet has been created, standard timesheet lines are added, deleted or changed (i.e. synchronize) with the assignments. However, for custom billing category
timesheet lines, they do not change when the assignments change, and they aren’t removed if the assignment is removed. We believe this causes secondary errors, like the "_Error Loading" (and others as will be described below).
3.When a timesheet with time in a non-standard billing category is deleted and recreated, time is arbitrarily moved to standard timesheet lines for the same assignment. If the task assignment is subsequently removed, the timesheet line causes the timesheet
to break.
4."Error Communicating with Server". When trying to submit a timesheet, a pop-up box appears indicating that there is an error communicating with the server. This error appears because a timesheet line is no longer associated with a project.
In order to submit the timesheet the orphaned timesheet line must be identified and manually removed. One technique we found which helps to identify an orphaned timesheet line is to select a task and submit task progress. Repeat for all timesheet lines until
you get an error. The timesheet line(s) with the error can be manually removed from the timesheet, fixing the error.
5. Unable to Open Specific Timesheets without Error. There are certain scenarios when the "Remove Task" feature is used or an assignment is otherwise removed after creation of a timesheet with custom billing category lines, which causes orphaned
timesheet lines. These orphaned lines can cause issues when trying to open a timesheet. The issue can appear when timesheets are in progress in multiple periods. In the problematic scenario, time is entered and submitted in one period and subsequently
the task is 'removed' from another period before the PM processes the first approval request. Process governance can certainly help here, but improvement in the way synchronization occurs between project assignments and custom billing category timesheet lines
would be great. The error can often be resolved by re-adding the assignment for the problematic timesheet user to the project (which creates a new assignment), and then allows you to open the timesheet. Then time can be moved from the old timesheet
line to the new timesheet line, and the old one can be removed.
In 4 and 5, sometimes we can't open a timesheet without error, and other times we can open it but not submit it. We are not 100% clear on all the different causes for each. Each of these issues are suspected to be contributing the the misalignment of
data between project actuals and timesheets, which can be a real problem for external projects for which time collected through timesheets are being used to generate invoices.
Although these may seem like separate issues, warranting separate questions, I decided to post them together because they all seem to be related to synchronization of project assignments and timesheet lines for custom billing categories.
Any thoughts or suggestions from the community would be appreciated.
Best regards,
Justin
Justin NaughtonThere are many causes for each of the errors mention. It would be best to put one issue to the forum at a time. For example, some of these issues occur then tasks are deleted from projects but a timesheet has been submitted. Depending
on the scenario, some of these issues have been fixed with the latest service pack.
Other issues are due to bad scheduling habits with the project managers and so first determining what they have done can help resolve some the issues.
_error Loading, is because something is NULL in the data and the jave is choking when it build the form. Again, these may be because of delete tasks, resources, projects or someone doing copying and pasting of rows.
cheers!
PS. Train your PM to not COPY and PASTE rows in project schedules. It can be done, but it can create problems. There are over 500 fields and some have unique data and the copy paste creates havic.
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries -
SD Release billing doc to accounting
Few billing documents failed and Accounting documents were not generated, I want to release the billing document to accoounting, in bulk, like around 2000 doucments, is there a transaction that I can use to upload the billing docs and release to accounting.
Hi,
You can release Billing Documents to Accounting by using tcode VFX3, Menupath: Sap easy access-Logistics-SD-Billing-
Information system - Worklists - VFX3 List Blocked Billing Documents.
Here you can select as per the Crieteria given Below:
1. You must have to give your respective sales organization
2. You can go as per Payer
3. you can do it as per User who creates billind documents
4. you can release it as per the from date and to date
5. you can realse by enter related billing documents
6. By Billing type
7. By Billing Category
8. Select All Incomplete due to
9. then clcik and Execute button or press Ctrl + F8
It will help you,
Regards,
MH -
Config of billing type G2 for Revenue Recognition
Hello Experts.
I have a situation where I need to configure billing of credits for revenue recognition.
For normal builling we have copied doc type SO to ZBCS and added ZTAD item category (copied from TAD) for the RR.
To do this for credits I copied doctype CR to ZBCR and assigned ZTAD item category to it.
When billing the ZBCR not I get the message "Item category ZBCR ZTAD cannot be invoiced with billing type G2".
How can G2 be configured to allow this?
This is G2's current setup.
Billing Type G 2 C red tM e m o Created by
Number systems
No.range int.assgt. 19 Item no.increment 0
General control
SD document categ. O C re dit m emo Posting Block
Transaction group 7 B il lin g doc um ent s Statistics
Billing category
Document type DG C us tom er cr ed it me mo
Negative posting N o neg at ive p ost in g
Branch/Head office C us tom er =Pa ye r/B ra nch =s old -t o p ar ty
Credit memo w/ValDat N o
Invoice list type
Rebate settlement Rel.for rebate
AcctDetermProc. KOF I0 0 A cco unt De e rm n ato n
Doc. pric. procedure
Acc. det. rec. acc.
Acc. det. cash. set.
Acc. det. pay. cards
Output/partners/texts
Output determ.proc. Z10 00 0 B il lin g Out pu t Application V 3
Item output proc.
Output Type
Header partners FK B iln g D ocu m en t
Item partners FP B il lin g Ite m
TextDetermProcedure 03 Invo c e hea de r
Text determ.proc.itm
Delivery textHi,
You may be maually given the PR00 in ZBCR. But in your copy control (VTFA) --> item category ZTAD --> pricing type, you may be maintained B (Carry out new pricing).
If you maintain B, you have to change it to "D ".
When you maintain B, the system will search the Pricing again in Credit memo. All manual prices will be lost.
Thanks
M. Lakshmi Narasimhan -
Differences between billing and accounting document with down paym. request
Hello to all
We are creating down payment request billing from one sales order with two sales order items that has different tax classification material.
The billing document is created correctly (with the same value for each item), not as the account document.
If you compare the value from the billing document to the account document is not the same. In the account document the system decreases the amount of the first item with the tax amount of the second item and the same for the second item (the amount of the second item decreases the amount of the second item with the tax amount of the first item).Then the tax amount of the two items is right.
If the two items have the same tax classification material, it works fine.
Can anyone help me?, is it a problem with the payment request billing?.
Thanks in advance.
Edited by: tonnetti pablo on Jan 8, 2008 9:46 AMHi,
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) For the `received down payments and `down payment requests from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) For posting key 19, set the sales order as an optional field
Maintain the field status definition (transaction OB14) For field status variant 0001, field status group G031, set the
sales order as an optional field
Assign the company code to the field status variants (transaction OBC5)
Regards,
Siddharth. -
Down Payment Processing in Milestone billing
I have created sales order that does milestone billing. The down payment is 10 % of amount - Billing type FAZ and condition type AZWR is included in Pricing Procedure and ERL is asigned.
I also have done all the required settings from the help file at:
http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm.
But the sales order still says G/L account not found and not saving. Is the G/L account need to found at sales order itself ? If so, where in sales oredr type I have to assigne account determination like KOFI00 etc ? Can any explain this ?
Does the down payment in sales order do the account determination to find G/L account as in case of regeualr billing docs ?The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
By useing tcode---> VKOA assing the G/L accounts for account deteramination -
Hi,
Please help me on this.
The advance payment in reference to the Sales order is maintained in Accounts receivables.The details of down payment(advance payment) is captured in SAP.The amount of advance payment is shown when account for customer is reconciled.The problem occurs when this invoice is again printed , after the final account reconciliation, as no advance payment amount is shown on the invoice though the balance figures are accurate.
With best regards,
ArcherHi archer naz
Check the following Customizing settings for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (t.code OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (t.code OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
Regards
Srinath -
hi gurus,
this is very urgent, in downpayment senario after sales order when i am going for order related billing it is stating that "document doesnot contains any item with open quantities"
plese resolve this problem asap.Hi,
Plz check in VBRK table whether doc no is saved in that table or not.Plz go through the Down Payments Configuration.
How Down Payments Are Configured
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling. The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
For configuring Installment Plans Please read following points
Regards,
Murthy -
Need config steps for Resource Related Billing
Hi Sap Gurus,
Can anybody explain me the step by step configuration settings for RRB.
Thanks
Hari Challa.HI REFER BELOW REWARD IF HELPS
Hi
Hope the following material will be helpful.
To activate the billing plan function, maintain the materials, for which
you wish to process down payments, with item category group 0005
(milestone billing). This gives the item type TAO via item type
determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for
down payments:
Maintaining the deadline type: This determines the billing rule
(percentage or value down payment) for the down payment request.
The system assigns billing type FAZ (payment request) defined in the
standard system with billing category P. (For the billing type FAZ there
is the cancellation billing document type FAS in the standard system).
Maintaining deadline proposal: Use the down payments that are due for
the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down
payment value already provided but which has not yet been calculated.
You must include this condition type in the relevant pricing procedure
before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48
(down payment clearing value must not be bigger than the item value) for
the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value
calculation formula 2 (net value). If the condition AZWR is changed
manually, you can get information on the original system proposal from
the subtotal.
Maintain the printing indicator.
The pricing procedure can not be marked as a transaction-specific
pricing procedure (field Spec.proc.)
The condition type AZWR has the calculation type B (fixed amount) and
the condition category E (down payment request / clearing).
No statistical or inactive conditions are set in a down payment item. If
you require these conditions, use the user exit USEREXIT_PRICING_COPY in
include RV61AFZA.
Maintaing the Billing Document
In the standard system there is the billing type FAZ (down payment
request) and for cancelling the billing type FAS.
Controlling the down payment is done using the billing category P of the
billing type. A billing type becomes a down payment request when the
billing category P is assigned.
You have to maintain blocking reason 02 (complete confirmation missing)
for the billing documents and assign it to billing type FAZ.
Copying control:
Copying requirement 20 must be entered in copying control at item level
for the down payment request. In the standard system the order type TA
for copying control is set up according to the billing type FAZ for the
item category TAO.
Copying requirement 23 must be entered in copying control at item level
for down payment clearing. In the standard system the order type TA for
copying control is set up according to the billing type F2 for the item
category TAO.
Financial Accounting settings:
A prerequisite for down payment processing is that the account is
assigned to the underlying sales document. To do this, change the field
status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR)
For the 'received down payments' and 'down payment requests' from the
G/L accounts you have selected, you should assign the field status
definition G031.
Maintain accounting configuration (transaction OBXB)
For the down payments (posting key ANZ in the standard system) and the
output tax clearing (posting key MVA in the standard system), you must
maintain the posting key.
You must also carry out a G/L account number assignment for the tax
account.
Maintain the posting key (transaction OB41)
For posting key 19 set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14)
For field status variant 0001, field status group G031, set the sales
order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5) -
Billing categories and license sets in UM 3.4 Beta
I have a hard time figuring out billing categories and license sets in UM. Please help
I'm running UM 3.4 Beta in my lab. The lab consists of two vCenter servers, vc01 and vc02. I have on ESXi host connected to vc01. This host is licensed with vSphere for desktop.
vc02 have five ESXi hots connected, they are all licensed with vSphere 5 Ent Plus. I've attached some screenshots of my UM.
Under billing Category in UM I set the vSphere for Desktop license to Perpetual and the Enterprise Plus license to VSPP.
I then created a License set named TEST where I only included the Enterprise Plus license.
Running a Customer Summary report without specifying a License set gives me a Billed vRAM (GB-Hours) of 14,734. Going back and choosing License set TEST
and running the same report gives me a Billed vRAM (GB-Hours) of 20,819.
Why is the second report reporting more billed vRAM then the first?There are many causes for each of the errors mention. It would be best to put one issue to the forum at a time. For example, some of these issues occur then tasks are deleted from projects but a timesheet has been submitted. Depending
on the scenario, some of these issues have been fixed with the latest service pack.
Other issues are due to bad scheduling habits with the project managers and so first determining what they have done can help resolve some the issues.
_error Loading, is because something is NULL in the data and the jave is choking when it build the form. Again, these may be because of delete tasks, resources, projects or someone doing copying and pasting of rows.
cheers!
PS. Train your PM to not COPY and PASTE rows in project schedules. It can be done, but it can create problems. There are over 500 fields and some have unique data and the copy paste creates havic.
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries -
Hello,
How can i create a link bitween SD billing and ISU billing for a specified ISU contract,and join the SD bill in the ISU bill document.
because the link exist only for the compte account.and sometimes we have more than one contract in the same compte account.
thanks for your response.Hi,
in SD:
SPRO: Sales and Distribution > Billing > Billing Documents
for you billing type you have to set U (IS-U billing document requirement) in field billing category: V_TVFK-FKTYP.
Define document type linked to you billing type in posting area 1210.
Define main an sub-transaction in posting area 1200 for SD.
the process is could be something like:
1. Create SD sales order
2. Invoice SD sales order using billing type defined as "IS-U billing document requirement" .
3. An entry is created in table EITR, BEL_ART equal to S (Even if S is not on the search help)
4. When you do invoice in ISU, both billing document from ISU and from SD are putted together in same print document.
Cheers,
Maybe you are looking for
-
Simple Transformation XML to ABAP Content of tag with subtrees to string field
Hi, I have an requirement in which I have to do a transformation from an XML file to an structure. I need get the value of a tag that have subtrees and move that to a field in my structure. Example: <TAG1>value1</TAG1> <TAG2>value2</TAG2> <TAG3>
-
How can I select rows of cells and merge them vertically into one cell in each column?
I'm working in CS4 and need to be able to select 2 to 6 rows of cells (with many columns) in a table and then merge the selected cells vertically into one cell in each column. A few cells in the chart will not need to merge so I must select the ones
-
CO-PA Characteristic hierarchies in reports
Hi Experts, I am aware that characteristic hierarchies can be used in CO-PA reports by specify in the hierarchy dialog box while defining characteristics in reports - but this is during creating/changing the reports My requirement is that I should be
-
Mp3 tag viewer with text encoding/decoding purpose
I'm want suggest some idea: Let assume that we have many mp3 files with cyrillic or some else non ascii tags in different encodings. And let assume that each file may have several encodings (eg cp1251 for album and utf-8 for title). Programs like Eas
-
How come I get the message (Not Charging) when I am plugged up to power?
How come I get the message (Not Charging) when I am plugged up to power? I keep getting this message, is there a problem? Or is this normal