CI template:
1. Requirements/Expectations
BSSL is having its operations in the soils of INDIA and as such IN is the country under which SAP R/3 47 SRII will work
BSSL has a substantial share of Exports in their business turnover and as such all the countries with which BSSL has business relationships need to be mapped in SAP R / 3
• General data
• Foreign trade characteristics
• Further test data
•
2. General Explanations
Standard settingsIn the SAP standard delivery system, all countries are defined according to the international
3. System Configuration Considerations
1 Check that the country entries are complete.
2. Add the missing countries, if necessary.
3. Use the ISO standard for your entries.
4. For each country, maintain the associated settings
4. Special Considerations
Nothing particular5. Project specific CI section
Not applicable
2. Currencies
CI template:
1. Requirements/Expectations
BSSL has to conduct its transactions in multiple currencies . The major ones being INR / USD / GBP / YEN / YUAN / Euro etc. The exchange rate conversions have to be maintained as per standard business processes to take care of statutory as well as Fiscal requirements
2. General Explanations
The currency table must have entries for all currencies which occur in your business transactions.
Standard settings
In the SAP standard recipient system, all currencies are defined according to the international norms
SAP recommendation
SAP recommends that you use the ISO standard for your additional entries.
If your entries do not correspond to the ISO standard, you will not be able to use data exchange in international communication (e.g. bank clearing transactions).
Actions
1. Check the currency entries for completeness.
2. Add the missing currency entries as required.
3. Use the ISO standard for your additional entries.
3. System Configuration Considerations
All posssible currencies should be mapped in the system to take care of an ever changing scenario. Entries can be subsequently added as per business needs.
4. Special Considerations None apparent at this time
5. Project specific CI section Not applicable
3. Units of Measurement
CI template:
1. Requirements/Expectations
Bhushan Steels will use SI units defined in the system and the standard conversion as provided by the system.
Some different unit of measure which are not standard units are also to be
List of the unit of measure attached.The units which are not standard are to be incorporated.
Attachments:
UNIT_MST LIST.xls
\\132.147.0.51\bsslsap\QAdb\Reports\Bhushan-MM\Stores\UNIT_MST LIST.xls
2. General Explanations
DefinationUnit that enables you to determine the size of a quantity of material.
Listed below are some of the units of measure included in the SAP R/3 System:
• base unit of measure
· · · · used by the system in managing stocks and
carrying out all its computations, other departments can use their own units of measure.
• unit of issue
· · · · Unit of measure in which a material is issued from the warehouse/stores. You can use this unit of measure in conjunction with goods issues and physical inventory activities.
• order unit
· · · · Unit of measure in which a material is ordered. It is the default unit in purchasing functions.
• sales unit
· · · · Unit of measure in which a material is sold.
It automatically appears as the default in a sales order and can be changed there.
·
3. System Configuration Considerations
Standard settings are available in the R/3 system. In case of any specific UOM it has to be configured and created in the system
4. Special Considerations
BSSL required some of there units of measure which they are using in there legacy system these units are required to be transmitted in the SAP R\3
.
5. Project specific CI section
None
4. Calendar
CI template:
1. Requirements/Expectations
BSSL is working three shifts and is virtually ona 24/7 production scenario due to the nature of the product being manufactured. It is suggested that a BSSL specific calendar is created in the system to take care of thier requirements in totality
2. General Explanations
A factory calendar is allocated to your plant via another Customizing function.
The calendar system consists of the following components:
• Public holidays
• Definitions for public holidays: Calculation rule for date, religious denomination etc.
• Public holiday calendar
• Any composition of public holiday rules.
• Factory calendar
• Definition of workdays including special regulations, under the assignment of a particular public holiday calendar.
· Standard settings
The system delivers definitions of all common public holidays and public holiday rules, as well as a standard factory calendar.
3. System Configuration Considerations
Standard setting to be used
4. Special Considerations
Nothing in particular5. Project specific CI section
Not applicable
5. Time Zones
Q: 1) Do you use the SAP System for global transactions covering several time zones? Are your customers, suppliers, plants or distribution centers spread over several time zones?
A: Standard IST to be used. Though our customers are located across the world there is no restriction of delivery processing , contact times etc to be maintained
CI template:
1. Requirements/Expectations
BSSL requires standard time zone functionality to be used for their system
2. General Explanations
Local data and times can only be compared with each other and exchanged if they are in the same time zone. Many global companies, however, work in different time zones. The SAP System supports the conversion of local data and times via the time zone function.
3. System Configuration Considerations
Standard settings to be used
6. Field Display Characteristics
CI template:
1. Requirements/Expectations
BSSL has a major concern over confidentiality of orders being booked and or Purchase orders prices being publicly known. A number of authorisations are envisaged. The filed display should be restricted to specific users in addition to the Authorisation matrix.
2. General Explanations
Field display characteristics can be defined globally or for a transaction. This technique was developed to hide the complexity of the SAP System from the user when possible.
Using transaction-specific field display characteristics ("transaction variants") you can preset fields in a transaction, define characteristics of fields, or hide whole screens in a transaction if they are to be skipped
3. System Configuration Considerations
Screen / Transaction variants will be configured based on requirements at the time of Base Line testing
4. Special Considerations
This activity is possible to work in tandem with the user IDs . Concurrent users may not be able to use this functionality.