Quantcast
Channel: SCN : All Content - SAP ERP SD Billing
Viewing all 2278 articles
Browse latest View live

Sales BOM --> Free rounding unit maintainence

$
0
0

Hi

 

in BOM , if for 10 "X"materials --> 1 'Y" material is free

 

           

In order, if i enter 20 materials "X" --> 2 " Y" materials are coming,

 

Need:

 

if i enter 25 materials . it is taking 2.5. However  i want it should be 2 .

 

system should take rounded value as 2.

 

Pls assist

 

Sachin


populate business place in billing document

$
0
0

Hi,

 

I have created a Sales order for TCS and want to populate Business Place in Billing Document. However, no field is available for the same. Some times people use business area as a deriving factor for the same with the code - GGB1. In our case, we are not using Business area as well. Is there any other war for the same. Please suggest.

Item 000090 Delivery Split due to conflicting header data (FKAIV IV)

$
0
0

Hello,

 

I am getting the above message. I would like to know where can I find the Inter Co Bill type (FKAIV) for the materials, so that I can see where it is different.

 

P.S. I am an ABAPer.

Accounting Document not cleared while billing

$
0
0

Hi Experts,

 

I am not an abaper!

I tried creating a sales order (sold to party is taiwan)  Had a credit hold , Released it , created delivery ,

Performed PGI, and finally i try to do the billing via VF01.

When i do the billing account docment got generated but says not cleared.....

I find these entries exactly.

cocd   itm       pk       account          amount        profit center     partnerpc         trprt             plant.

131     2        50       501210          1,000.00-      24002     24002          121             2075

131     1         01       12100099          1,000.00                                          121     

 

I am tryin to understand what went wrong?

Is there some information available from this to find a fix?

 

regards,

Shawn.

Billing date correspond to 2030, why?

$
0
0

When a billing documen is saved shows an error regrading to an incosistency between the document date (29.04.2013)) and the last assigned date (29.04.2030).

To correct:

I enter in the header and change the billing date and in the level item, Serv. rendered date was change, too.

Both dates 29/04/2013.

 

After that, document pass to FI.

 

But this is just a partial solution, becuase the system continues getting the year 2030, for all invoices generated, since yeasterday.

This is so strange for me.

 

I've read some of your comments in other answers and I've reviewed dates, and all seems to be ok.

 

I'm a basic user, So, I'don have access to customizing things

The keyuser don't have any idea =(

 

For now, we are just correcting manually this invoices to be able to pass to FI

 

Please, help me into this strange issue.

 

Thanks!

Business Area not populated in customer line item

$
0
0

Dear All,

 

We have upgraded the system from 4.5 B to ECC 6.0. the following issue occurred.

 

Business area is not populating in customer line item in its accounting document for some materials. But there are cases when the buss. area is populating for the same materials.  I have a case when there is 1 sale order with 1 material, it was delivered partially that means it has two dispatch notes so it has two invoices.  But the problem is business area is populating for one invoice but on other its not populating both invoices are of the same date as well.

 

Kindly help.

Tool cost piece rate control

$
0
0

We have tooling cost invoice, where in the tool cost per piece will be maintained in the condition type master.  and when invoice is raised the piece rate for the invoice quantity will be calculated and based on which ed,cess willbe calculated.

 

 

We need to fix a control that for certain quantity alone the tool cost price to be calculated after which the rate should be picked as 0. Do we have any user exit or is there any config changes required.

Error Cancel Billing Document

$
0
0

Hi,

I have the following problem when I delete the invoice (VF11) in relation to the position TATX (text):

- sales order without TATX position;

- delivery with additional TATX position;

- positions copied from delivery to billing (including TATX);

- when i try to cancel the billing the log shows the following messages:

    - Data inconsistency during processing of document 0090011112 (Message: VF-188 / Output type: E / Group type: F).

    - Order item 0080029201 000020 is missing (Message: VF-029 / Output type: E / Group type: F).

.

When TATX position was inserted in the sales order SAP let me delete the invoice.

 

Thanks.

 

Best regards.

 

Antonio


Foreign trade data error in Cancelled Invoice - Not editable

$
0
0

Hi All,

 

We are not able to pass a cancelled billing document to accouting due to foreign trade data error.

When we try to open the same in VF02 and chang all are greyed out and nothing is editable.

 

Please help.

 

Thanks

Account determination for condition based down payments

$
0
0

Hi experts,

 

please help me with down payment procedure, which I try to set according this link http://help.sap.com/erp2005_ehp_06/helpdata/en/46/27dcd449fc14dce10000000a155369/frameset.htm

 

So we make SO with AZWA condtion

enter down payments in F-29 with reference to SO number, Item number and schedule line

Then Vl01n, GI

When I create billing doc. using VF01 I expect to see down-payments received for SO in AZWB condition, but AZWB is empty.

When I fill AZWB value manually it is not posted in accounting.

 

So, my questions are:

1) Any ideas why AZWB is empty? I use formula 49 for calculation. Can this error be caused by some wrong settings for item category of billing doc?

2) What settings should I make, for create postings in accounting, that described on help.sap.com? Should I assign special accounting key in accounting determination for AZWB condition?

 

Would be very grateful for answers,

 

BR, Ivan

Accounting document generation in credit card process

$
0
0

Hi,

 

we are using credit card process and have a scenario, I understand as standard process in credit card process the accounting document generated will have a debit and a credit entry for the customer account. The issue is when there are multiple deliveries against one order and while invoicing if i invoice VF01 with single Delivery eg 100$ then in the accounting document the customer is debited and credited (100$+ and 100$ -),

 

customer acct-xyz 100$

customer acct-xyz 100$- (minus)

 

But in case iam clubbing 2 deliveries against the same order and the value of the two deliveries are 50$ for 1st and 200$ for second delivery, when i bill these 2 deliveries with VF01, the accounting document generates two entries for each of the delivery. it shows up as\

 

customer acct-xyz 50$

customer acct-xyz 200$

customer acct-xyz 50$- (minus)

customer acct-xyz 200$- (minus)

 

Can someone help me in understanding if this is the standard behaviour / process for multiple deliveries combined in one credit card invoice.

 

Regards

VV32 Billing output determination

$
0
0

Two output types are available in the system:

 

ZRD0

ZRD1

 

The first has been available for some time and has been working correctly to default as generate output when document is created.

 

New requirement for new form was configured for ZRD1. The output determination was configured for the new output and VV32 updated by BillTo so it will geneate ZRD1. When the document is saved, it continues to print out the ZRD0. What configuration is missing so that it will print the ZRD1?

 

Thank you,

 

Bela

Free Goods scheme for 3-4 different materials on 1 material

$
0
0

hi

 

I want to give free goods scheme of 3-4 different material on one material at one time in sales order.

 

Example : For Material "A" (50 qty) <----- materials B (2 qty) + Material C (1 qty)+ Material D (4 qty) + Material E (1 qty) are free

 

What needs to be done? pls assist

 

Regards

Sachin Karale

How should I restrict invoicing before PGI?

$
0
0

Hi,

 

SAP is presently allowing me to generate invoice prior PGI is performed. Could you please guide how should I restrict this in copy control settings? Also, once invoice is generated before PGI, it triggers revenue generation too. I want to restrict this and bring in between a proforma invoice after delivery instead of invoice. What should I do? Will that stop revenue generation?

 

Thanks for your expert suggestion/comments.

Resource related billing SD-PS

$
0
0

Dear gurus,

 

can any of my guru share me the documentation, containing end to end information, regarding how i configure the system for resource related biiling, how should i create material, price, billing process and rest of the factors.

 

looking for the kind response from gurus.

 

regards,


Business Area not populated in customer line item

$
0
0

Dear All,

 

We have upgraded the system from 4.5 B to ECC 6.0. the following issue occurred.

 

Business area is not populating in customer line item in its accounting document for some materials. But there are cases when the buss. area is populating for the same materials.  I have a case when there is 1 sale order with 1 material, it was delivered partially that means it has two dispatch notes so it has two invoices.  But the problem is business area is populating for one invoice but on other its not populating both invoices are of the same date as well.

 

Kindly help.

unit pricing displaying wrongly on the invoices.

$
0
0

Hi Team,

 

In some invoices unit price is displaying wrongly  (i.e, its printing Unit price before discounts ) instead of unit net price.

 

For example base price is  $ 100 $ &  Net value is $ 95 . So on  the invoice it should print Unit price as $95 (after all discounts) , but

 

System is printing it as $100 (before discounts)  for only few invoices.  I have checked basic config settings & necessary areas not able

 

to identify why its happening only for few invoices.

 

If  you have any valuable inputs in such similar issues please step in & share the same.

 

 

Thanks

Retro-Billing SD (VFRB)

$
0
0

Applies to

SAP ECC; Sales and Distribution; Billing.

 

Summary

Retro-billing is a process of issuing credit or debit memos after retroactive price adjustments

 

Created on

07 May 2013

Author(s)

Jyoti Prakash

 

Author Bio

Jyoti Prakash is SAP Certified Associate and works as Senior Resource for Order Management & After Market. Currently, focused in providing consulting services to their customers for support project on SAP Order Management, After Market, Project System, and Logistics Execution.

 

 

Table of Content

  1. Introduction
  2. Overview
  3. Prerequisite for using on Retro-Billing
    1. Billing Document for Retroactive pricing adjustment
    2. Condition record
    3. Order Reasons
  4. How Retro-Billing works on SAP
    1. Invoice & condition record - Existing
    2. Condition Record - Change
    3. Executing of Retro-Billing
  5. Related Content

 

1. Introduction

Out of those various business processes in billing is accommodates & reconciliation of the retroactive prices adjustment for number affecting existing invoices. The retroactive prices adjustment can be due:

  • Strong bargaining power of customer over
  • New pricing agreement between supplier
  • Volatile/change is price of essential commodities for manufacturing

to name a few.

 

This kind of prices adjustment can be handled by Retro-Billing. For instance, a new pricing agreement that you agreed with your customers may affect billing documents that have already been processed and settled. If that pricing agreement is effective before the pricing date of the billing documents, you can perform retroactive billing to call up a list of these documents and revaluate them with the new price. You can then create additional billing documents to settle any differences.

 

So, by definition & example of retro-billing, it can have a life cycle of months or sometimes beyond a year. Therefore this makes it a unique process.

 

2. Overview

retro01.1.png

Figure 1. Retro-Billing Process

 

On Jul 01, 2011, Supplier ships & sells 10 units of Material ABCD to Customer XYZ for $100 per unit (valid from 01.04.2011 to 31.03.2011), total amount $1000.

 

On Jul 07, 2011, invoice is sent to Customer for $ 1000.

 

Now on Aug 17, 2011, due to negotiations price may change to $120 w.e.f. 17.08.2011 (valid till 31.03.2012). Thus you will update your condition type in TCode VK12 for this Material ABCD & Customer XYZ to $120 with validity from 02.04.2011 to 31.03.2012. But as you have already invoiced the customer in past so, to take care of this retroactive price adjustment you have an extra billing. 

 

So, standard SAP platform provides the retro-billing transaction VFRB. This transaction provides basic retro-billing functionality enabling identification of invoice documents affected by retroactive price changes and execute creation of multiple documents.

 

In Retro-billing, enter the selection criteria like Payer, Sales Organization, Billing date from & to, Pricing type, Currency, Sold-to Party & Material.

 

By this system will provide you the list of invoices to which this retroactive price changes is applicable and hence you can simulate or even execute retro-billing & system will accordingly generate Credit/Debit memo type based on differential amount.

 

For positive retroactive price changes, i.e., $ 20 per unit price from former as $ 100 & revised as $ 120. In this case system will generate Debit Memo for the differential amount to be collect receivable from Customer. Whereas, for negative retroactive price changes, i.e., $ 15 per unit price from former as $ 100 & revised as $ 85.For this case system will generate Credit Memo for the differential amount to be pay back the differential amount to Customer.

 

These documents will get be in document flow of the original invoices.

  

3. Prerequisite for using on Retro-Billing

A. Billing Document for Retroactive Pricing Adjustment

      1. Retro Debit Memo
      2. Retro Credit Memo
      3. Corresponding relevant Copying Control
      4. Pricing procedure for capturing price change

  

B. Condition Record

      1. The value for base price should determined automatically in the invoice through condition record
      2. It should be maintain on the bases of Material & Customer combination
      3. It should be a have valid validity from & to date

 

C. Order Reasons

You need to maintain proper order reasons specific to retro billing document type for Credit/Debit memo.

 

4. How Retro-Billing Works on SAP

A. Invoice & Condition Record - Existing

You can use TCode VF05N for list of billing documents or invoices based on 

      • Billing Document Date (to & from)
      • Billing Type,
      • Customer & Payer,

To view desired invoices with current base prices use TCode VF03.

In invoice, check item data – condition tab to view pricing.

retro02.png

In the invoice, to view corresponding maintained condition record for condition type, say, ZPR0. Selecting the condition type and click on retro03.pngbutton to view the maintained condition record.

retro04.png

 

B. Condition Record - Change

For changing in the existing condition record for base price condition type use TCode VK12. Choose key combination as Customer/Material. retro05.png

Provide the desired parameter for execution the condition records.retro06.png

Maintain the change in price difference. Say, positive difference of 10.00 from former price 58.00/- and revised price 68.00/-.retro07.png

 

C. Executing of Retro-Billing

Use TCode: VFRB for exercising retro-billing option. Provide following parameter based on your requirement, but keeping mandatory fields in mind:

    • Payer (Mandatory)
    • Sales organization(Mandatory)
    • Billing date from(Mandatory)
    • Billing date to (Mandatory)
    • Pricing type(Mandatory)
    • Currency(Optional)
    • Sold-to party(Optional)
    • Material (Optional)

retro08.png

You have a option of include Invoices with the Same Net Values. This indicator defines whether invoices whose current net value is the same as the post-calculated net value should be included in the retro-billing list.

    • If the indicator is set, invoices with the same prices are included.
    • If the indicator is not set, invoices with the same prices are not included

For instance, Invoice was created with a price of 100 Units. After the unit price is reduced to 50 Units, the retro-billing list is used to create a coupon for 50 Units. If you discover later that this price reduction was incorrect and you set the price back to 100 Units, a retro-billing list only appears if this indicator is set.

retro09.png

Below you can find details of entries without error

retro10.png

Select the desire invoice/invoices for the list of entries without error and click on retro16.png button for simulation run.

 

Then following screen will appear for simulation run.

retro11.png

For generating Retro Debit/Credit memo click on retro12.png button.retro13.png

You can click on retro14.pngbutton for viewing the generated retro billing. Green indicator confirms that the document generated without any
errors
.
retro15.png

Subsequently you can view the generated Debit memo from retro billing by using TCode VF03.

 

 

5. Related Content

 

 

 

 

 

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

 

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

 

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

payment terms

$
0
0

Dear sd gurus i have one doubt regarding payment terms

we maintain payment terms in customer master in company code level and sales org level..

and in vk11 also if we maintain vk11 system is taking payment terms only from vk11 not in customer master level

if we not maintained in vk11 then system will take from customer master sales area

then my doubt is what is use of maintaining payment terms in company code level ?

thanks a lot

Example of RVAB02 PP from IDES

$
0
0

Hi,

 

This discussion is raise in reference to an existing discussion

- Example of RVAB02 PP from IDES

rasied by Vaishnavi Tangirala

 

Hi

Can anyone give me an example of how RVAB02 PP works from IDES? I want an example how accounting entries look like for Sales price inclusive of tax.

I have a problem now that tax code is not getting copied to the Revenue line in accounting doc since iam calculating tax on gross price and not on price after tax.

I will be very grateful for any help regarding this.

Thanks,

Vaishnavi

 

May I know how was this issue resolved? I am encountering the same problem now.

 

Thanks,

Leng

 

Message highlighted in blue was edited & added by: Jyoti Prakash

Viewing all 2278 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>