Professional Documents
Culture Documents
different date
When using transaction VF04 or Billing (background), the date of the billing document
(e.g. the current date) must be entered (In VF04 : settings, default data.)
In VF06 or background: variant with parametrization) to avoid an unwanted split due to
the billing date.
This OSS notes is very helpful :11162 - Invoice split criteria in billing document
36832 - Invoice split in fields from the sales order
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.
ENDFORM.
This is how it should look after modification:
* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
PSTYV LIKE VBAP-PSTYV, <- New line
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
ZUK-PSTYV = VBAP-PSTYV. <- New line
VBRK-ZUKRI = ZUK.
ENDFORM.
After this routine is created and activated place it as the default copy control routine
instead of the old ones.
If you hit the above erros when you create an invoice in SD, the corresponding
accounting document is not created.
The error is as follows:
Maximum number of items in FI reached Message no. F5 727
Diagnosis
The maximum number of items for an FI document ('999') has been exceeded.
System response
FI documents have a 3-digit item counter that limits the number of items permitted per
document.
Procedure
If the documents with an excessive number of items come from another application area
(e.g. sales, logistics, order accounting), you can configure the system to the effect that
these documents are summarized in FI. "
How could this error be solved as none of your invoices are getting accounted in FI?
To overcome this, the only way was to break the accounting invoices, 1 with 950 items
and the other with the rest.
- We receive the sales orders and produce a Pro Forma invoice from it, and send it to
customer
- Once we receive the payment, we release the sales order for delivery and produce the
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.
And after that go and check in the particular Sales order document type whether billing
document types are maintained in the sales document or not.
If every thing is correct go and find with copy controls
If it order related, go VTFA
If it Delivery related, go VTFL and check in your document type combination is
maintained or not, if they are maintained item category is available or not.
After delivery while creating billing document system showing error that no billing
document is generated for material no 395. So how I can solve this issue.
Check if Item Category is checked for Billing or not.
Normal Sales Order Cycle:Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business
transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type,
always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion
with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions:
Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order
Types to required Sales Area. This will minimize selection of Sales Order Type as per
sales area.
Sales Document Item:
*1. Define Item Categories: If possible use Standard Item Category. Incase if required to
create new, copy as from standard & maintain New.
*2. Assign Item Categories: If possible, use standard. Formula for deriving item category:
Sales Document Type + Item Category Group + Usage + Higher Level Item Category =
Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if
required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving
Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
*1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to
create new, copy as from standard & maintain New.
*2. Define Item Categories for Deliveries: If possible use Standard Item Categories for
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.
You can delete the Sales Order if transaction have been done:
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.
You can create individual Billing documents in VF04, with out any saving of each and
every billing document.
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.
12) Criteria -- In criteria allocate the activity type for the specific material. (We can also
use cost element, cost center, which we have defined in characteristics)
13) Create Project (T.code CJ20N)
14) Create Sales Order (T.code VA01)
15) Book CATS
16) Execute DP91 to view Sales Pricing
Common Errors:
AD01-155: Error during material determination for sales document item. Material
Origin field was not checked in the Costing tab of the material master.
IX-057: No cost management is provided for sales document (contract) item. This is
usually because there is no requirements type assigned to the contract item (see
procurement tab).
No material appears in DMR/CMR. In the material master costing view, set the
"Material Origin" checkbox (see OSS note 174382)
No expenditure item found.
Go back to the service order and check there are actual costs
Check your DIP Profile; specifically the sources section to ensure you are not filtering
out any dynamic items.
CO Configuration:
KL03: Check activity type validity dates
KA03: Check cost element validity dates
KA03: For labour, check cost element category is 43
KA03: Check if Record qty flag is set on Indicators tab
KA03: Check cost element assigned to your controlling area
KP26: Check that activity type is linked to cost centre
KP26: Check that there is a rate for the activity type/cost centre
KP26: Check are you using the correct version
Company code:
Credit control area:
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
*} INSERT
* Read the subsequent function information for the message
PERFORM FOFUN_TEXT_READ USING GL_FOFUN
CHANGING FOFUN_TEXT.
MESSAGE ID 'V1' TYPE 'E' NUMBER '849'
WITH FOFUN_TEXT
RAISING ERROR.
*{ INSERT DEVK966908 2
*} INSERT
ENDIF.
ENDFORM.
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-----
Action: Define a credit control area and its associated currency. The Update Group
should be 00012. This entry is required so the sales order will calculate the value to
authorize
Assign Company Code to Credit Control Area
Transaction: OB38
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
1) You have a Customer which you had felt, he is doing good business and supplied
material on Credit of 45 days.
2) Since this customer is good as you felt, you have not managed Credit Checks as well.
So, he had comfortably reached to the fullest credit (or even more) which you can afford
for any customer.
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.
The credit exposure is updated based on the update algorithm assigned to the credit
control area.
000012 - updated at Sales Order
000015 - updated at Delivery
000018 - updated at Billing
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.
What is CIN?
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios.
Excise related configuration is known as CIN configuration. CIN Configuration is a topic
in itself.
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.
- Multiple GR for one excise invoice, Single credit
- Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each
excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to
maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and
PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every
business to maintain only one set of excise registers and one set of accounts. But through
exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one
excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI
as blank. If you receive multiple GR's for a given Excise challan and would like to avail
multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple
credit'. Alternatively if you want to availa the credit only after all the goods receipts
have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of
billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately
and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto
post'. This will post the selected records into RG23D automatically. You cannot cancel
the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan
quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for
RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements
automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of
material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material
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.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you
tick the 'No utilization' indicator.
- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly
payment then mark the 'Immediate Utilization' Iindicator. Example - You could define
two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
- No account postings for CENVAT in sales cycle
- No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just
generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group
but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the
system immediately pays the amount from CENVAT and creates the Part II entry. Such
invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the
account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being
done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty
indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings >
Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining
excise duties and sales taxes on input materials in India.
- If you use condition-based excise determination, use a copy of the tax procedure
TAXINN.
- If you use formula-based excise determination, use a copy of the tax procedure
TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can
work with both concurrently.
We strongly recommend that new customers use condition-based excise determination.
Note that once you have started using a tax procedure, you cannot switch to another one,
otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and
pricing condition types are used in calculating excise taxes using formula-based excise
determination.
If you use condition-based excise determination, fill out the CVD cond.
field and leave all the others blank.
If you use formula-based excise determination, fill out all of the
fields as follows:
- Enter the tax procedure and the pricing conditions that are relevant
for excise tax processing.
- Specify the purchasing and sales conditions types used for basic
excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise
rates.
- Specify the countervailing duty condition type used for import
purchase orders.
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.