Professional Documents
Culture Documents
1.
2.
3.
4.
5.
6.
7.
8.
Order
Item
Turbine
100,000
Billing Plan
Billing date Description
Billing Status
01-10-94
Contract
01-03-95
Assembly
01-04-95
Maintenance
01-05-95
Acceptance
01-06-95
Final invoice
Value
10
30
30
30
..
10,000
30,000
30,000
30,000
..
Billing Block
x
x
x
x
Milestone
x
x
x
x
Network/Activities
Milestone
Assembly
Maintenance
Acceptance
Estimate
01-03-95
01-04-95
01-05-95
Actual
01-03-95
For each billing date in a milestone billing plan, you can specify
whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is
earlier than the
planned billing date for the date
In Customizing for Sales, you control how the system automatically creates the schedule
of dates in a billing plan. The system determines the schedule of individual dates based
on general date information, such as the start and end dates. This general date information
is copied either from contract header data or from proposals in the billing plan type.
Pricing
Sales document items are billed as each billing date in the plan becomes due. The system
determines the amount to be billed either from the condition records that are applicable to
the item or from the values that are explicitly entered in the billing plan for a particular
billing date. In milestone billing, for example, you can specify a percentage to be billed
or an actual amount.
Billing block
A billing block can be set for each date in a billing plan. The block prevents processing
for a particular billing date but does not necessarily affect any of the other dates in the
plan. In milestone billing, the system automatically sets a billing block for each billing
date. This block remains in effect until the project system reports back that the milestone
in the corresponding network has been successfully completed. At this point the system
removes the block.
Billing index
For every billing date in a plan, the system creates and updates a billing index. If a billing
date is blocked for billing, the system copies this information into the index.
Billing status
The system assigns a billing status to each billing date in the plan. The status indicates to
what extent the billing has been processed for that particular date. After billing has been
carried out successfully, the billing status is automatically set to C. This prevents a
billed date from being billed again.
Billing Rule for Milestone Billing
For every date in the milestone billing plan, you can specify a billing rule. The rule
determines how the billing amount for the particular date is calculated. For example, you
can specify whether the billing amount is a percentage of the total amount or whether it is
a fixed amount.
In addition, you can specify that the amount to be billed is a final settlement that takes
into account billing that has not yet been processed. For example, price changes may take
place after billing dates in the plan have already been processed. The price differences
can be taken into account during final settlement.
Final settlement is not automatically proposed in the billing plan by the system; you must
enter it manually during processing.
Fixed dates in milestone billing
You can control for each date in a billing plan, whether the date is fixed or whether the
system copies the date from the planned or actual milestone dates in a project.
Document flow
After a particular date in a billing plan is processed for billing, the system updates the
document flow for the corresponding sales document item.
The document flow for the sales document displays the following data:
Creation date
Billing date
Billed value
invoices.
- We post the payment we received earlier against this last invoice.
As you see, this requires a lot of manual work and a lot of time is wasted to match all
documents together. There most be a more efficient way to handle this, anybody have any
hints?
-----Reply Message----Subject: RE: Prepaid process possible
Hi again!
You are right! However, if you create a new item category for the prepaid scenario, you
can
select what item category (and process) to use at order entry. It is also possible to code a
user exit so that only certain customers will get the prepaid process. This can be done also
with item category groups (can be used to determine what default item category that
should appear). This would mean that you either have different materialnumbers for the
different processes or use different distribution channels in the sales order. DC 10 could
be
the normal process and DC 20 the prepaid process. Then you need to create the sales
views in material master for DC 20 for all materials that should be possible to run in the
prepaid scenario, and enter the "prepaid item category group in the sales item category
group field in material master.
Here is a proposal of customizing activities to achieve this:
1. Create a new item category as a copy of the normal item category used for non-prepaid
sales. (Change the billing in the item category to order related billing with no billing
plan)
2. Create a new item category group "ZXXX" or something of your choice with the
description "Prepaid" or something like that.
3. In item category assignment, add or check entries so that you have the order type used,
and item category group defaulting the new item category.
4. Check copy control from sales document to billing document for the new item
category.
Also delivery copy control could be good to check.
5. Create a new distribution channel and assign it to the company structure (plant, sales
org etc)
6. Extend your material(s) with views for the new distribution channel and enter the
"ZXXX"
item category group in the field for sales item category group (I think it is on sales 2
screen
but I am not sure, can't access a system right now).
Now you should be able to create a sales order with the new distribution channel where
the new item category is defaulted. Check that the sales order is completed when both
billing and goods issue for the delivery is posted. If not check the completion rule in the
new item category.
Delivery Type. Incase if required to create new, copy as from standard & maintain New.
*3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create
new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls
such as Sales Order to Billing, Deliver to Billing, etc.
Note: Ensure that Copy Control settings are done
Sales Order to Sales Order (QT --> OR): VTAA
Sales Order to Delivery (OR --> LF): VTLA
Sales Order to Billing (OR --> F1): VTFA
Delivery to Billing(LF --> F2): VTFL
Billing to Sales Order (F2 --> RE): VTAF
The configuration differs from scenario to scenario & requirement of the
client.
In VA02 , just enter into the sales order goto menu path -> Files-> Cancel or delete option
will be there will be there.
After deletion / cancellation of that sales order that order doesn't exist in the database.
For example , if your sales order number is 1055 and you have deleted or cancelled that
sales order, then that sales order number doesn't exist in the database and you cant create
another sales order with the same order number 1055. When you create another sales
order the number will skip to the next one i.e, 1056.
You can only reject the Sales order if there are existing transations:
1. First you need to cancel the billing document using T-code VF11, so it will reverse all
the updated accounting entries.
2. Now you need to cancel the Post goods Issue using VL09, once it is reversed, the
delete the delivery using VL02N.
3. Once the delivery is deleted, the sales order will be open. Now put a reason for
rejection in the line item/s, and reject the order, the order will get closed. It is not
advicable delete a sales order.
Match Billing Cancel Document
How to find out the link between the original and cancelled billing documents?
Goto to tcode SE16
Table: VBRK
Field: VBRK-ZUONR - Assignment (this field link the original and cancelled billing
documents)
Cancel billing documents must be successfuly released to accounting. Usually it failed
when user tried to cancelled current period with previous date.
Select all the deliveries which you want to create billing documents, using Cntr Button,
and click on individual billing. Then all the deliveries will go for billing individually in a
single run. And you can also see all the billing documents numbers, which are created.
No need to select single delivery each time.
If you want to do a batch job for billing, proceed for the following process
1. goto VF04, in the selection screen Delivery document range, for which you want to
create billing documents e.g., in SD Document field, give delivery 1 to 10.
2.Now Click on GOTO -> Variant -> Save as Variant, then it will take you to another
screen, give the variant name, e.g., test, and save it.
3. goto SM36, this is used to do batch job, if you dont know any thing also, you can do
the entire process, using JOB WIZARD, click on Job Wizard which is on the screen.
4. It will take you to different steps, just you need to give your variant name, (in job name
field) (in the first screen) the continue for further steps, In the ABAP Progamme Name
give SDBILLDL, (this is the programme used to create billing documents) continue to
give the specified time which you want to run this batch job, like immediate, after an
hour, or a specific day like so.
5. Continue further to complete the task, now you batch job will run at a specified time
which you mentioned, if you mentioned as immediately, then once you comple this
process, your vairant will run, and billing documents will be created.
6. Plese ensure that all the deliveries are perfect, meaning there is no billing block or any
thing.
You can check the status of your batch job using t. code SM37.
Difference between the RSNAST00 and SDBILLDL program.
RSNAST00 is a program which is related to output related activities. Using this program,
we can schedule the creation of outputs (PDFs, email etc) in total for any document
created in any of the applications. The details are read and stored in the database table
NAST. The same program is customised for each applications using programs like
SD70AV1A which are also used for the same purpose but only for sales orders.
SDBILLDL is the program for Billing due list. This program finds out all the orders or
deliveries or both which are due for billing and it will trigger the billing creation. It reads
tables like VBAK, VBAP, VBUK, VBUP, LIKP, LIPS etc and the created billing
documents are stored in tables VBRK, VBRP.
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in
Transaction
OB45, or the credit control area must be entered under the relevant company code in
table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the
limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is
marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on
"Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used
for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition ->
Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area?
The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
CHANGING FOFUN_TEXT.
MESSAGE ID 'V1' TYPE 'E' NUMBER '849'
WITH FOFUN_TEXT
RAISING ERROR.
*{ INSERT DEVK966908 2
*} INSERT
ENDIF.
ENDFORM.
-----Original Message----Subject: Sales value field in not getting updated after creating the billing
we are on 4.6b. we are going for credit management but facing one problem. in fd32customer credit management change - the sales value feild in not getting updated after
creating the billing.
eg. when i create the order - the order value get updated in the sales value in fd32. after
creating the delivery - that value remains same in the feild of sales value. but when i am
going for billing (delivery related), the bill value is appearing in 'receivables' but the
amount
in 'sales value' is not getting reduced. because of this the credit exposure is increasing
continuously.
update group for corrosponding credit ctrl area is 12. also the item is mark for credit
update.
can anyone tell the missing link?
thanking in advance
-----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing
Hi,
You need to check couple of settings like:
1. Your customer should be assigned the credit control area.
2. In your Item Category Credit should be active.
Regards,
-----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing
customer is assign to concorn CCA and item category is mark for credit active
-----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing
Hi,
Check the credit update group in the transaction OB45. The credit update group controls
when the values of open sales orders, deliveries and billing documents are updated. It
should be '000012'.
Further also refer to the OSS note 18613.
Have fun
-----End of Message-----
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination,
create a subtotal line to store the value of the price plus any sales tax. Make the
following entries:
Sub to: A
Reqt: 2
AltCTy: 4
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document
types for which credit checking should be bypassed. You need to mark the field no
Credit Check with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form 02 defined for payment cards. Other than the
descriptor, the only other entry should be 3 in the column labeled PymtGuaCat
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number 1
Payment Guarantee Form 02
Routine Number 0 Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = Payment Card Payment Cards (All Customers
can use Payment Cards).
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant
for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for
payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment
guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length
and prefix (etc)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
3) One fine day you got realised that, there is very bad debt with this customer and need
to recover from him and till then, there will be no further supply to the customer.
4) Your company's legal department has laid a policy that, inorder to recover any bad
debts, like:
a) We will send a normal payment reminder.
b) In case customer doesnt respond, we will send at least further reminder (dunning
notice) may be 9 times
(9 reminders) (Dunning level) and what intervels of time (dunning frequency)
c) Still if the customer doesnt resopond for the reminders, you will file a law suit against
the customer for recovering
the Payments.
d) Finally, after getting veridict, you may proceed for auction of his property or as per the
order for Law.
Now in SAP, the definition of Dunning procedure is a pre-defined procedure specifying
how customers or vendors are dunned.
For each procedure, the user defines
- Number of dunning levels
- Dunning frequency
- Amount limits
- Texts for the dunning notices
In SAP, you will maintain the Dunning Procedure at customer master. Referring to this
your SD Team / FI Team (user team) will effect Dunning
PS: You might remembered the dunning procedure laid by Relaince Mobile, sometime
back, sending street rowdies for recovering the bad debts from users. That is dunning.
Remember Reliance, you will not forget dunning forever.
To look at only Receivables for a customer look in FD32. If you have bad data run the
reorganization program through SE38.
Check Note 425523 - Collection of consulting notes: Credit update and related.
Surely you must run report RVKRED77 (Note 400311 - RVKRED77: Reorganization
credit data, new documentation and related will help you).
1. How is credit exposure calculated (seen in FD32)?
Its simple summation of Receivables + Special liabilities (like down payments, advance)
+ Sales value
2. If Update=000012 in CCAr then on creating Sales Order, the exposure increases
by SO value.
But if update=000015, then also on creating Sales Order, the exposure increases by
SO value.
Is this correct?
I think in case of 000015 Open sales order values should not be considered.
3. What role exposure play in the credit management process. I mean does the
system match the value of credit exposure with credit limit to find that it is exceeded
or it does it differently?
Credit exposure is in fact the main player. In credit management if the customers credit
limit is 10000 and credit exposure is 9900 then customer can only be able to buy now
worth of 100 only. Its the credit exposure which should not crossed over the credit limit.
For reporting purpose, where we can get customer credit exposure which showing in
FD32.
Go to t.code F.31 for an overview of the credit exposure, and also you can use
s_ALR_8701212218 to overview the credit exposure.
Some info on CIN Configuration (it may not appear as understandable below, but if you
check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
- Enter each of your excise registrations, specifying a four-character code for each Excise
Registration Ids
In this activity, you maintain excise registration IDs. You create one ID for each of your
business's excise registrations.
- For each excise registration in your business create a registration ID, and state:
- Which taxes the registration covers (additional excise duty, special excise duty, and
cess) Fields for any taxes that are not covered will be hidden in transactions involving
excise duty.
- The maximum number of items to be printed on each excise invoice
- Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has
registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is
located.
Excise Collectorate: The code of the excise collectorate in whose area the excise
registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to
basic excise duty and special excise duty. Example - Additional Excise duty is livable in
case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum
number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and
Distribution (SD) for factory sales and for other movements. This information is used to
split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only
a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on
the material into its deductible and nondeductible amounts. It posts the deductible duty to
the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in
Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use
In excise journal voucher transaction. It provides the flexibility to the user to enter the
debit account of his choice depending on the nature of transaction.
Automatic balance Indicator - Excise year start month. The calendar month marking the
beginning of the excise year. This start month represents the month for the start of the
excise invoice number range. The month 04 is entered here indicating April of the
calendar year as the start month for excise invoices. Any change by the Excise authorities
regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure :Excise invoice selection type. To indicate the method
opted by the company for selecting the excise invoice. It can be either earliest or latest
invoices that were received. Number of excise invoices to be selected Indicates the
number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection Number of days from document date
for excise invoice selection.
Example - If the value of this field is 20 and today is 28-03-97. The excise invoice
selection will show the related invoices only for the period 08-03-97 to 28-03-97.
Document type for TDS FI posting: Financial accounting document type for TDS
posting.
Document type for FI posting on Utilisation Financial accounting document type for TDS
posting.
Indicator for item level excise duty round off - This indicator is to be used for deciding
whether Item level excise
duty amount rounding off is required during procurement cycle. If marked 'X' then the
excise duty amount will be rounded off to the nearest rupee at the Purchase order level.
This will not round off the CENVAT credit to be taken. If the duty amount is less than
one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise
amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for
each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods - Instructs the system, when you verify a goods
receipt for capital goods, to immediately post half of the input excise duty to the
appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use
in the following year.
CVD Clearing Account - Specifies which G/L account the system credits when you take a
CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type - Key representing a type of exchange rate in the system.
- You enter the exchange rate type to store different exchange rates. Example - You can
use the exchange rate type to define a buying rate, selling rate, or average rate for
translating foreign currency amounts. You can use the average rate for the currency
translation, and the bank buying and selling rates for valuation of foreign currency
amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an
Excise invoice for export sales then the exchange rate for duty calculation will be picked
up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to
your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
- Specify whether it is a manufacturing site or a depot.
- Assign it an excise registration ID. - You can assign the same ID to more than one plant,
if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare
register RG 23D, and follow different procedures for goods receipt and invoice
generation.
- Number of goods receipt per excise invoice.
Then, in transactions involving excise duty, for example, when you post a vendor's excise
invoice, you specify which excise group you are using. This information tells the system
which G/L accounts to post the excise to. At the end of the period, when you come to
prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG
23D, and follow different procedures for goods receipt and invoice generation.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales
and Distribution (SD) excise invoice immediately you create a commercial invoice or a
pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this
function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution
(SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will
create Depot excise invoice by posting the selection of excise invoices in single step. If
this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic
posting of RG23D selection then the Post Goods Issue should have been completed
before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt
using 'MB01' system will default the excise invoice quantity on to the Goods receipt
document.
Folio number for depo Posting - If this indicator is marked then while creating Excise
invoice for other movements system automatically does the Verify and Post. You need not
separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
- Blocked stock
- Stock transport order
- Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups
within your company. Series groups allow you to maintain multiple number ranges for
the outgoing excise documents. Based on excise regulations and exemptions from the
authorities you can maintain multiple number series for outgoing documents. But each of
these series has to be declared to the excise authorities.
A return is a sales document used in complaints processing for when a customer sends
goods back.
You enter a return in the system if the customer returns damaged goods, or goods that had
been delivered for sale on approval. The return causes the system to: Register the receipt
of goods using a returns delivery, and post the goods to stock (for example, blocked
stock).
Create a credit memo, once you have checked the goods and approved the complaint. A
return is another type of sales document like a standard order.
The return triggers the following functions:
- Delivery (returns delivery)
- Billing (for creating a credit memo)
When you create a return based on a complaint, you: Post the goods to your warehouse
for checking And then, implement one of the following activities:
- Approve the complaint and create a credit memo
- Approve the complaint, and implement a free of charge subsequent delivery based on
the return
- Reject the complaint
PGI (Post Goods Issue) may be cancelled by Transaction code VL09. The accounting
document is just the reverse of the original PGI document.
In my company, we use project stock (movement type 601 Q for PGI). VL09 creates the
movement type 602 Q. But rather than VL09, the generally accepted method in my
company for the reverse items is to use the movement type 653, "back to the to the
storage location." The accounting document takes the cost "from" the project and moves
it back "to" the storage location.
The movement types are entered in the schedule lines in customizing, which are then
assigned to the item categories. However, in this process, "no invoice" takes place. If you
have a delivery related invoice, it should be cancelled beforehand.
If you do not give replacement, the Customer Account needs to be credited.
Please do not forget to create a Billing document (Formally Return Credit Memo) with
reference to return delivery. It is very important in order to close the cycle. If you do not
create a return credit memo, your delivery will keep appearing in the "Billing Due" list
and with status "Being processed". When you create a return order type RE, the billing
type is picked up as RE (Return Credit Memo) automatically.
When you are creating a replacement, you can create a replacement order, delivery, and
billing. To create the replacement order, you can define an order type by copying from
order type OR. In the copy control, you can define the relevant item categories from RE
to OR. You can make reference Mandatory for this order type. The delivery type for this
replacement order type will be LF and billing type F2.
The movement types are entered in the schedule lines in customizing, which are then
assigned to the item categories. However, in this process, "no invoice" takes place. If you
have a delivery related invoice, it should be cancelled beforehand.
If you do not give replacement, the Customer Account needs to be credited.
Please do not forget to create a Billing document (Formally Return Credit Memo) with
reference to return delivery. It is very important in order to close the cycle. If you do not
create a return credit memo, your delivery will keep appearing in the "Billing Due" list
and with status "Being processed". When you create a return order type RE, the billing
type is picked up as RE (Return Credit Memo) automatically.
When you are creating a replacement, you can create a replacement order,
delivery, and billing. To create the replacement order, you can define
an order type by copying from order type OR. In the copy control, you
can define the relevant item categories from RE to OR. You can make
reference Mandatory for this order type. The delivery type for this
replacement order type will be LF and billing type F2.
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data
elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure
PRODHS.
You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3.
Proceed as follows:
Create the following domains:
ZPRODH3 with length 5, category CHAR,
ZPRODH4 with length 3, category CHAR,
Change structure PRODHS:
Structure PRODHS in the standard system:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 8
Changes according to example:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
PRODH2 PRODH2 CHAR 5
PRODH3 PRODH3 CHAR 5
ZZPRODH4 PRODH4 CHAR 3
validation. Secondly, validity periods must be established to indicate when the allocation
control records are active. Finally, the user has the option of establishing a conversion
factor per allocation control record to accommodate BOM listings of constrained
materials
6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the
standard order processing functionality, the requirements class must have a flag
indicating that allocation is relevant.
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation
in the standard order processing functionality, the schedule line must have a flag
indicating that allocation is relevant
8.Create Planning Hierarchy (MC61) In order to adequately establish allocation
quantities, the user must initially determine the level at which the allocation is to take
place and the aggregation factor of the allocation quantities. In this step, the levels for the
collective allocation search procedure are also identified.
9.Generate Masking Character (OV7Z) Upon completion of the level determination for
the planning hierarchy, the collective allocation masking character must be generated to
allow aggregation indicators to be established. This transaction simply reads the
hierarchy established in the planning table and then generates a collective mask character
for each level of the hierarchy
10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial
hierarchy was established. In order to complete the hierarchical set up, the collective
allocation (mask character) hierarchy must now be maintained with the appropriate
aggregation factors
11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the
allocation process are the materials. Each material that is to be considered in allocation
scenario must be mapped to an allocation procedure. In order entry, then, when a material
is entered with a valid allocation procedure in the material master, the allocation data is
verified prior to confirming the line item ordered
12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS
information structures that can be used in the product allocation process. This report
simply reads through the data dictionary and selects all the active information structures
that contain the field product allocation object (KONOB) as the first field. This data can
then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step
to an information structure (previous step).
Whether it can send pdf or other file format will depends on the Mail Server you are
using.
The basis people must also maintain the conversion parameters so that SAP knows how
to convert the billing documents to be send as a pdf file or other desired format specified
by your company.
Finally, you have define the IMG in Maintain Output Determination for Billing
Documents (Output type MAIL)
Example
Date
SalesOrderNo Material Amount Currency
10.01.2007 8530
732
1000
INR
*&---------------------------------------------------------------------*
*& Report ZCHE_SALES_ORDER
*&--------Done by V.Chellavelu on 11.01.2007
--------------------------*
REPORT
zche_sales_order
****************************Declarations********************************
TABLES: vbkd,vepvg.",vbak,vbap,vbpa,vakpa, vapma.
DATA: BEGIN OF sal OCCURS 0,
ch TYPE checkbox,
vbeln LIKE vbak-vbeln,
netwr LIKE vbak-netwr,
matnr LIKE vbap-matnr,
waerk LIKE vbak-waerk,
dat
LIKE vbak-erdat,
END OF sal.
DATA: newsal LIKE sal OCCURS
ENDIF.
ELSE.
IF vkorg <> ''.
PERFORM cus_orga.
ELSE.
PERFORM cus_orga_else.
ENDIF.
ENDIF.
* Displaying the contents which is selected from table by
* -selection conditions
SORT sal BY dat.
LOOP AT sal.
ON CHANGE OF sal-dat.
*
FORMAT HOTSPOT ON.
IF sy-tabix = 1.
WRITE: sy-vline, sal-ch AS CHECKBOX,sal-dat .
CLEAR amount.
ELSE.
WRITE:sy-vline, amount,/ sy-vline, sal-ch AS CHECKBOX,sal-dat.
CLEAR amount.
ENDIF.
ENDON.
amount = amount + sal-netwr.
AT LAST.
WRITE:sy-vline, amount.
ULINE.
SUM.
*
FORMAT HOTSPOT OFF.
FORMAT COLOR = 3.
WRITE:/ ' Total Amount:', sal-netwr UNDER amount.
ENDAT.
ENDLOOP.
**********************Interaction with report**************************
SET PF-STATUS 'BANU'. " To create Application ToolBar for Display
Button
*
To verify Double click on BANU
AT USER-COMMAND. " This will execute after pressing Display Button
CASE sy-ucomm.
WHEN 'DISP'.
free newsal.
DO.
READ LINE lin FIELD VALUE sal-ch INTO checkbox.
IF sy-subrc NE 0. EXIT. ENDIF.
IF checkbox = 'X'.
PERFORM datecon.
PERFORM process.
ENDIF.
lin = lin + 1.
ENDDO.
PERFORM selection.
ENDCASE.
************************ SUB ROUTINE Area
******************************
*This Process SubRoutine will assign the values from current
*
-InternalTable (sal) into other IT(newsal), by date which is
*
- selected by CheckBox
FORM process.
LOOP AT sal WHERE dat = dat.
newsal-ch
= 'X'.
newsal-vbeln = sal-vbeln.
newsal-netwr = sal-netwr.
newsal-matnr = sal-matnr.
newsal-waerk = sal-waerk.
newsal-dat
= sal-dat.
APPEND newsal.
ENDLOOP.
ENDFORM.
"process
*&---------This will display the values for selected dates from new --*
*---------------------internal Table (newsal)-------------------------*
*&
Form SELECTION
*&--------------------------------------------------------------------*
*---------------------------------------------------------------------*
FORM selection.
ULINE.
FORMAT COLOR = 1.
WRITE:sy-vline,'Date',AT 14 sy-vline, 'Order NO', AT 27 sy-vline,
'Order Material', AT 48 sy-vline,'Order Value(AMT) Currency '.
FORMAT COLOR OFF.
ULINE.
LOOP AT newsal.
ON CHANGE OF newsal-dat.
IF sy-tabix <> 1.
WRITE:/ sy-vline, AT 14 sy-vline,AT 27 sy-vline,AT 48 sy-vline.
WRITE:/ sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline.
ELSE.
WRITE: sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline.
ENDIF.
ENDON.
WRITE:/ sy-vline, AT 14 sy-vline,newsal-vbeln,sy-vline,
newsal-matnr, sy-vline, newsal-netwr, newsal-waerk.
AT LAST.
SUM.
ULINE. FORMAT COLOR = 3.
WRITE:/ sy-vline, AT 15 'Total Amount for selected month:',
newsal-netwr UNDER newsal-netwr.
FORMAT COLOR OFF.
ULINE.
ENDAT.
ENDLOOP.
lin = 1.
FREE newsal.
ENDFORM.
"SELECTION
* This Date convertion is must for pick the particular Date from the
*
-displayed line, and here we are reversing the Date like
YYYY/MM/DD
* -because to Check or assign the date we need to give in reverse
order
*&--------------------------------------------------------------------*
*&
Form DATECON
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM datecon.
date2 = sy-lisel(17).
SHIFT date2 LEFT BY 4 PLACES.
WHILE date2 <> ''.
SHIFT date2 RIGHT.
date4 = date2+11.
IF date4 <> '.'.
CONCATENATE date4 date3 INTO date3.
ENDIF.
ENDWHILE.
date5 = date3(2).
date6 = date3+2.
date3 = date3+4.
CONCATENATE date3 date6 date5 INTO date3.
dat = date3.
* SORT dat BY dat.
* DELETE ADJACENT DUPLICATES FROM dat COMPARING dat.
ENDFORM.
"DATECON
* Here we are doing different kinds of selections by the EndUser's
needs
*&---------When user selectiong an Sales Organisation-----------------*
*&
Form ORGANISATION
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM organisation.
SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln,
sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN
vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON
f~vbeln = p~vbeln WHERE p~audat IN date AND p~vkorg = vkorg.
APPEND sal.
ENDSELECT.
ENDFORM.
"ORGANISATION
*&---------Without Sales Organisation i.e All Organisation------------*
*&
Form ORGANISATION_ELSE
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM organisation_else.
SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln,
sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN
vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON
p~audat IN date.
"ORGANISATION_ELSE
"CUS_ORGA
Output is a form of media from your business to one of its business partners or it can be
within the organization. The output can be sent to any of the partners defined in the
document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery
Notes, Invoices & Shipping Notifications. Determining form of output is output
determination.
Types of Output:
Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange)
--> PRINT OUTPUT:
Configuration path: ( following are the steps)
1) SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output
Determination using Condition Technique- >Output Determination for Sales Documents
(or you can use output determination for billing documents depending on your
requirement).
2) Create Condition Table: select the field Sales Doc Type from field catalog & Save
3) Maintain Access Sequence: 4-digits code & description.
4) Assign condition table to access sequence. Select Accesses line item and Go To Fields.
Fields will display the fields we have selected in the condition table i.e. sales doc type.
Maintain Output Types:
AF00: Inquiry
AN00: Quotation
BA00: Order Confirmation
LD00: Delivery
RD00: Invoice
Select BA00 & Copy & Rename. Give the same 4-digit code as given to access sequence.
You Can Maintain:
Languages of Output
Partners (to whom you need to send output)
Can we get the print if the order /delivery is blocked after static
credit limit check?
Please follow the below path:
IMG - Logistics Execution - Shipping - Deliveries - Define Reasons for Blocking in
Shipping - Execute
- Define Reasons for Blocking in Shipping Here select the delivery block that is blocking your order/delivery, and uncheck if the
option Print is checked.
Display View "Deliveries: Blocking Reasons/Criteria": Overview
DB Delivery block descr Order Conf.
Print DDueList
SpK
SpW
01 Credit limit
02 Political reasons
03 Bottleneck material
04 Export papers missng
05 Check free of ch.dlv
06 No printing
07 Quantity Change
08 Kanban Delivery
Printing block field:
Indicates whether the system automatically blocks output for sales documents that are
blocked for delivery.
Example :
In the case of sales orders that are blocked for delivery because of credit reasons, you
may want to block the printing of order confirmations.
Note:
The particular output that is affected by a delivery block is determined in output control.
PS: If the document is exceeds by the credit limit output type will not determine and as
well as we should not give the output type in sales order. We have to assign the routine 2
to sales order output types and 3 routine to delivery output types to restrict from output if
the docuement exceeds by credit limit.