Posted by sapadmin on February 3, 2011
Use
You can carry out credit checks from Sales and Distribution (SD) in the following scenario:
Central Financial Accounting and decentralized SD processing
The decentralized Sales and Distribution units all have independant credit management. This
means maintenance of credit master data, checks in SD, and realeasing via the credit manager
are all carried out decentrally.
As only credit-relevant data for the corresponding Sales and Distribution unit is available for
credit checks on the decentralized Sales and Distribution units for the sales order, delivery and
goods issue, and credit account data is also needed from the head office (for example, sum of
open items, oldest open item, maximum dunning level), Financial Accounting (FI) makes the A/R
Summary available.
With the help of the A/R Summary, the credit data can be collected in the central system, and
sent, via ALE distribution functions, to decentralized Sales and Distribution processing, and can
be evaluated. The A/R summary presents the inquiry in Financial Accounting for credit checks.
As the credit-relevant SD data (open sales order, delivery and billing document values) is not
distributed, there are specific prerequisites for working with distributed systems.
Prerequisites for Working With Distributed Systems
When working with distributed systems, one of the following terms must be fulfilled:
• The decentralized Sales and Distribution units must be available via separate credit control
areas (there must not be a multiple assignment).
or
• Different customers must be assigned to each of the decentralized Sales and Distribution
units (there must not be a multiple assignment).
or
• Credit checks in the decentralized Sales and Distribution units can be carried out with
reference to FI data (for example, static credit limit check without open credit values from
Sales and Distribution, dunning level etc.)
Posted by sapadmin on February 3, 2011
[#2: Edit Options>MightyAdsense>Adsense Code]
Definition
An organizational unit that represents the area where customer credit is awarded and monitored.
This organizational unit can either be a single or several company codes, if credit control is
performed across several company codes. One credit control area contains credit control
information for each customer.
Use
Credit and risk management takes place in the credit control area. According to your corporate
requirements, you can implement credit management that is centralized, decentralized, or
somewhere in between.
- For example, if your credit management is centralized, you can define one credit
control area for all of your company codes.
- If, on the other hand, your credit policy requires decentralized credit management,
you can define credit control areas for each company code or each group of
company codes.
Credit limits and credit exposure are managed at both credit control area and customer level.
You set up credit control areas and other data related to credit management in Customizing for
Financial Accounting. For more information, see the Implementation Guide under Enterprise
Structure →=Definition or →=Assignment →=Financial Accounting and then Maintain credit control
area. You assign customers to specific credit control areas and specify the appropriate credit
limits in the customer master record.
Structure
The following graphics illustrate the relationship between credit control area, company code,
sales organization, customer and currency for central or decentralized credit management
respectively.
Posted by sapadmin on February 2, 2011
[#3: Edit Options>MightyAdsense>Adsense Code]
Batch determination is a usability check. You can use this function for all
outward movements to find batches that meet certain specifications. The
functionality is identical in all applications.
You can run batch determination in the following areas:
-Inventory Management
-Production
-Distribution
-Warehouse Management
Search strategies are the cornerstones of batch determination. Search strategies
are master data and contain information on the selection criteria you
want to use to find batches and on the further handling of the batches found
(for example, wether batch splits are authorized). Search strategies are
defined for individual business transactions.
In process manufacturing, you can use batch determination to find batches
of material components to be handled in batches. There are several methods
you can use to store the selection criteria required for batch determination.
The system automatically checks batch availability during batch determination.
The figure 7-5 shows the screen generated after you trigger batch determination
in a process order.
Batch Determination.
Posted by sapadmin on February 2, 2011
Batch management contains cross-application functionality available as of
Release 3.0 and is integrated with all logistics-related applications:
-Purchasing
-Inventory Management
-Production
-Sales & Distribution
-Warehouse Management
-Quality Management
SAP’s usage of the term batch (lot) concurs with the following definition
published by the Food and Drug Administration (FDA) in their Good Manufacturing
Practices (GMP):
“Batch: a batch is a quantity of any drug produced during a given cycle of
manufacture. The essence of a batch is its homogeneity.”
For SAP a batch is thus a quantity of any given material, produced during
one production process. It is characterized by clearly defined specifications.
Using Batch Management, you can manage partial quantities of a material
seperately in stock.
The figure below shows how batches are created during a production process.
Depending on the requirements of your industry, you can also combine
batches of materials that have identical specifications during quality inspections.
Posted by sapadmin on January 26, 2011
When you install an SAP System with MS SQL Server, the central components of the database
are the SQL Server program files, tempdb files, SAP data files and transaction log files. The
log files record all the changes made to the database to enable restore and recovery. The
tempdb holds all temporary tables and stored procedures. The data files contain the data for the
SAP System.
• SAP Data Files
The data files are created in the directories \DATA. The first data file is called
DATA1.mdf and subsequent filesDATA.ndf, where denotes
the number of the file. The minimum space required for all files is 9 GB.
For security reasons, locate the data files on a separate disk system. They should not be
included in the same disk system as the log files or other SQL server program and database
files. To ensure data redundancy, SAP recommends the use of RAID 5.
• Transaction Log File
The transaction log for the database is created in the directory \LOG1. The log
file is called LOG1.ldf and requires a minimum of 1 GB space.
The transaction log file records all the changes made to the database and, if required,
enables modifications to be redone or undone. It plays a crucial role when the database has
to be restored due to database damage or media failure. For this reason it should be stored
very securely. SAP recommends the use of RAID 1 which implements hardware-based
mirroring.
• DBMS Files
The files other than the SAP data and transaction log files are created in the directories
\MSSQL7 and \MSSQL7DB. These include the SQL Server program files and the master,
msdb and tempdb database files. Locate these on a separate, third, disk system and not on
the same disks as the transaction log files or SAP data files. SAP recommends the use of
RAID 1.
For performance reasons, it is advisable to place the tempdb files on a fast disk system.
This is particularly recommended because the tempdb is frequently accessed during SQL
Server operation and could otherwise affect performance.
Posted by sapadmin on January 26, 2011
The configuration of the system is generally planned well in advance of the installation together
with the hardware vendor. Configuration planning involves deciding whether a central system or
standalone database system is to be installed, and how many dialog instances and frontends
are required.
The configuration is worked out with the hardware partner on the basis of sizing information that
reflects the system workload. Details such as the set of applications that are to be deployed, how
intensively these are to be used, and the number of users enable the hardware vendor to
recommend a configuration that performs well. To simplify the process of planning an appropriate
configuration, SAP provides a Quick Sizer tool that helps to determine the right combination of
resources such as CPU, disk space and memory.
Posted by sapadmin on January 26, 2011
Purpose
Before you begin with the practical installation tasks, it is essential to have a planning phase in
which you make a number of fundamental decisions that influence the subsequent installation
procedure. Careful planning is a prerequisite for the successful installation of the system.
Process Flow
When you plan the installation you have to:
• Decide on the optimal configuration for the system
• Decide whether a domain or local installation is suitable
• Make sure that you can meet the hardware and software requirements specified by SAP
• Work out how the software components must be distributed to disks
• Decide whether you want to integrate Active Directory Services
Posted by sapadmin on December 20, 2010
Transaction ME12 – Purchasing Info Record -> In the Control Section, look for the field Tax Code
Maintaining the Tax Codes :-
Transaction SM31 – Table T007A – Tax keys
Click Customizing
Transaction FTXP – Maintain Tax Code
Posted by sapadmin on December 20, 2010
You must post a subsequent adjustment to correct the goods issue posting when the vendor informs you after goods receipt that a greater or smaller quantity of the components was actually consumed than planned in the purchase order.
To do this, proceed as follows:
MB04 – Subcontracting Subsequent Adjustment
Fill in the Purchase Order Number and hit enter
Tick the checkbox of the components you want to adjust and click the Adopt button or press F5
Enter the quantity difference. If more of the components were consumed, enter a positive amount, if fewer were consumed enter a negative amount.
Finally, post the document.
Posted by sapadmin on December 20, 2010
Pricing Release Procedures
4.6.x
Define Processing Status – SM30 -> V_T686E
You are free to design your own processing status flow.
from 01 -> 02 or
from 01 -> 02 -> 03
To convert the old Pricing Condition with the release status use program SD_MOVE_A004_TO_A304.
For the standard tables, the following pairs of condition tables are intended to be used:
‘old’ <--> ‘new’ VAKEY fields
A004 <--> A304 VKORG + VTWEG + MATNR
A005 <--> A305 VKORG + VTWEG + KUNNR + MATNR
A006 <--> A306 VKORG + VTWEG + PLTYP + WAERK + MATNR
A007 <--> A307 VKORG + VTWEG + (SPART) + KUNNR
For example, if you are using A005 –> A305, you have to copy the program to ZSD_MOVE_A005_TO_A305 and amend the program Source and Target table.
First test run by ticking both option. If you confirm that there are no errors, then run by unticking both options.
Be careful while executing the conversion program as it can erase all your existing pricing condition data.
Once the conversion is completed, you can activate the Customer/Material with release status :-
IMG -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Access Sequences -> Maintain Access Sequences
In VK12, you will be able to choose the new Customer/Material with the release status column per material.
Posted by sapadmin on December 20, 2010
If you want a material to be blocked, go to the Basic data 1 view of the material,there in the genral data you have ” Y-plant material status “. Also in Cost estimate 1 view of the material you have Plant Specific Material status. Use the options available to block the material in these two views.
You cannot use the material in sales order
Use the material exclusion function:
FUNCTIONALITY:
SD> Master data > Products > Listing/Exclusion> Create
( Transaction codes VBO1, VB02, VB03)
Enter the list-exclusion type B001: For the required
Customer;
Enter Maintain materials > Save > Exit
Create the order and enter material excluded to test exclusion.
CONFIGURATION: IMG SETTINGS
For IMG settings; Go to IMG > SD > Basic Functions>Listing/Exclusion
ENsure that the listing/exclusion procedure is activated for your order type. You can also create your own condition types access sequences and procedures or use the SAP provided ones.
Posted by sapadmin on November 23, 2010
Objective
You can use this component to calculate the remuneration for work done for each employee.
However, Payroll does not just involve the calculation of remuneration, but consists of a variety of
processes that are becoming increasingly important due to the employer’s increased obligation to
supply benefits and medical welfare. These benefits are products of:
- Labor law
- Tax law
-Contribution law
- Benefits law
- Civil law
- Reporting law
- Information law
- Statistics law
» Read more…
Posted by sapadmin on November 23, 2010
An HR budget structure element is an object in an HR budget hierarchy.
Use
You can use budget structure elements to show the hierarchical relationships that exist in a
budget hierarchy. Once you have defined the budget hierarchy, you can assign budgets to the
budget structure elements in it.
These budgets represent preliminary estimates for personnel expenditure in a financial year.
They are expressed in the budget currency. You use the budgets of the budget structure
elements to finance persons and positions. » Read more…
Posted by sapadmin on November 23, 2010
| ABAP_DOCU_DOWNLOAD |
Download ABAP documentation in HTML format. |
|
| APPL_LOG_DELETE |
With this function module you delete logs in the database according to specified selection conditions |
|
| APPL_LOG_DISPLAY |
With this function module you can analyze logs in the database. |
|
| APPL_LOG_DISPLAY_INTERN |
With this function module you can analyze logs in local memory, e.g. when you have only collected log records at runtime and do not want to write to the database. |
|
| APPL_LOG_INIT |
This function module checks whether the specified object or sub-object exists and deletes all existing associated data in local memory. |
| » Read more… |
