Customization -configuration

Hi,
Please explain in detail about customization and conifguration.
Regards
Vijaya

Hi Vijaya,
Its the way in which you can make changes to SAP standard software.
Tcode - SPRO
What is customizing ?
Customizing is the setting of system parameters via SAP's own interface.
What is confguration ?
This is very specific to the Business where certain Fields / properties are enabled or activated as per the requirement.
We can say that Customizing is at General terms and Confguration is specific.
Hope this helps.
Manish

Similar Messages

What is difference between customization & configuration

what is difference between customization & configuration ???

Hi Sahu,
The difference between cutomizing and configuration is:
CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data.
CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
Also, When considering enterprise software of any type, it is important to understand the difference between configuration and customization. The crux of the difference is complexity.
Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets.
Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.
Regards
Sasikanth.Ch

Difference between customization & configuration

What is the difference between customization & configuration?

The difference between cutomizing and configuration is:
CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data.
CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process.
Also, When considering enterprise software of any type, it is important to understand the difference between configuration and customization. The crux of the difference is complexity.
Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets.
Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors.
Regards,
Gauravjit
Reward Points if the answer is helpful.

Regarding Liquidity Planner Customization (Configuration) ?

Hello ,
    Every one
        Currently i am searchiing basic neccessary Liquidity Planner Customization to be do . My question is could any body tel me the way how should i get the names of all necessary Liquidity Planner Customization ?
        If any body has list of it could you tel me the names ?
Thank you
Deepak Pawar

The best thing you could do is read the configuration guide for [FSCM-CM|http://help.sap.com/bp_bl603/BBLibrary/HTML/160_ES_VE.htm].
Hope it helps!

CIN customization / configuration - details

Dear SAP Gurus,
I was going through the CIN details from search pages of this forum and some how I was not able to correctly follow. If it is possible I will request you all to send me any info you have including any links and/or material about how to customize and configure CIN in general to my mail ID [email protected] and I WILL for ever be so so greatful. Customization material will be really helpful.
Thanks and regards.
Venkat.

In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing Scenarios. 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
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
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.
Activities
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
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.
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 leviable 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 leviable 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
Use
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
Use
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.
Use
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
Use
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.
Activities
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.
Dependencies
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
Use
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.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. 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 through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
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.
Dependencies
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.
Dependencies
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 Groups
Use
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.
Activities
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' indicator.
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
Use
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
Use
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
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
Make the settings in Customizing Basic for Logistics General, by choosing Taxes on Goods Movements AccountIndia Settings Determination.Excise Duties Using Condition Technique and
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the access from the SAPExcise Rate Maintenance screen, which you can Master Data Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
Material master data
Each material is assigned a chapter ID.
Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
For taxes on purchases, use the condition types contained in the tax procedure.
For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
VS1 (basic excise duty)
VS2 (additional excise duty)
VS3 (special excise duty)
VS5 (sales tax setoff)
MWS (central sales tax)
MW3 (local sales tax)
ESA (service tax)
ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
Excise group
Company code
Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
Defined the G/L accounts
Defined the excise groups
Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
1. Go to IMG Define Logistics General  Material Master  Configuring the Material master ScreenStructure of Data Screen for each Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
Please reward if helpful

SCCM 2012 R2 - remote control port[s] - customize/configure/change?

First, let me start by saying I am aware of
this page that outlines the ports used in SCCM. It has a section called "configurable ports" and another called "non-configurable ports". However, remote control (port 2701) isn't listed under either - its under another section.
Currently, we have another app utilizing the same port[s] that the SCCM remote control piece uses. I want to know if there is any way to configure this to use a different port? Somewhere in the registry perhaps? From what I've read it doesn't sound like
it is changeable but I wanted to confirm in here.
Our other app is configurable, however, it would require us to not only change it on each of the 100 or so Windows servers, but over 900 Unix servers as well that are configured to use the same port. So it will be a little bit of work. The other
option (as I have it set up now) is to just leave remote control disabled.
Thanks in advance!

Is 2701 the default port for this application or is this just bad luck? If it is the default port would you mind sharing which app this is for our information.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Is work flow configuration & custmization T.Codes in srm same as in r/3

Hai Gurus
Need clarification ,is work flow configuration & custmization T.Codes in srm same as in r/3.
For example:Starting condition defining in srm is through SPRO>SRM>SRM server>Cross appl basic settings>sap business work flow
And in R/3 it is through T.Code PFTC
Thanks in Advance
chandra

Hello Chandra,
T-codes for workflow customization & configuration are similar in SRM and R/3. There are multiple ways to check each transaction.
Thanks,
Shital Nimje
Edited by: Shital Nimje on Sep 21, 2009 5:41 AM

Customize ICSS (E-self service)

I must Customize ICSS (E-self service) V.4 SP12 with SAP CRM 4, I want document help or guide for modify. Please inform with me.
Regard,
Soothiluck

Hello Soothiluck,
You are in good luck. Here is the link to the document from Best Practice Library. This is for customization (configuration).
[CRM 4.0 E-Service Configuration Guide.|http://help.sap.com/bp_crmv340/CRM_DE/BBLibrary/Documentation/C74_BB_ConfigGuide_EN_US.doc]
Well, if you really meant modification by saying "customization" (European semantics) - then, there is no special Enhancement guide as it is available for E-Sales, but the concepts are pretty much same (at 10,000 foot level). Both are STRUTS based, Java Web applications with SAP CRM as the backend system. The comparison stops there. However, that is the only document we have. So, here is the link to the "customization" guide.
[ E-Selling Development & Extension Guide|https://websmp101.sap-ag.de/~sapdownload/011000358700001432572004E/ISA40_DevGuide_v1_1.pdf]
If you already knew about this and looking for a E-Service specific guide, sorry, you are out of luck
Easwar Ram
http://www.parxlns.com

Deploying application with Customizations

Hi All,
I was working with Customizations and I have a base application on which I added some customizations (seeded only). I created a MAR profile and included that within my EAR. On my integrated weblogic server it works fine.
Now when Im trying to deploy this on a standalone instance of weblogic server, the deployment fails and Im getting this message.
oracle.mds.internal.lcm.exception.ValidationException: MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration._ at oracle.mds.internal.lcm.deploy.DeployManager.predeploy(DeployManager.java:353) at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:162) at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160) at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188) at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199) at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused By: oracle.mds.config.MDSConfigurationException: MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration. at oracle.mds.internal.lcm.MDSLCMManager.getConnectionInfo(MDSLCMManager.java:1953) at oracle.mds.internal.lcm.deploy.DeployManager.predeploy(DeployManager.java:310) at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:162) at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160) at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188) at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199) at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any ideas what might be going wong over here.
Thanks.

Hi,
did you deploy the EAR file to the integrated WLS and this worked? Or did you run the application and have JDeveloper do the deployment ? Is there anything specific to your customization configuration and which version of JDeveloper 11 do you use (see help--> about)
Frank

Meeting Place meeting ID customization

All, a different request I have been asked and am now asking you. A client would like to limit the Meeting IDs given out when a meeting is scheduled to 50 specific number strings. They have been running like this on their old meeting system for quite some time and require this feature moving forward. Apprently, they have a backup (hosted) system to which calls are re-routed where the meetings IDs are mirrored so no communication needs to be sent out to the meeting participants.
The scenario is - reception creates a meeting with a meeting ID of 10001 (for instance) and communicates that to the end user. If Meeting Place were to cease functioning prior to or during the meeting, they require that users would be able to dial the same number (after the telco have re-routed the destination to the backup hosted system) and input the exact same ID they were given by reception.
My question is, can this be done in MP and if so - where is this customization configured.
Thanks in advance for the asssitance.
Geoff

what does the Username for the dedicated email account for Cisco Unified MeetingPlace on the Microsoft Exchange Server indicate?
Example: [email protected]
Does that means that email notifications sent by meeting place will be sent by the email address [email protected]?

OTL customization using AK Developer or OAF?

Hi all,
Currently I have a change request that required me to customize Employee Self Service |TimeCard into Daily, Weekly, and Monthly Format.
Which mean, I need to create/customize/configure a TimeCard region that handled Daily Entry, Weekly Entry, and Monthly Entry.
Understood that OTL Timecard is configurable via AK Developer and LCT/LDT file.
But in these kind of situations, where I need a logic to
1) A selector/LOV/Tab Panel to display Daily, Weekly, or Monthly
2) A customize layout for daily, weekly and monthly
3) A customize CO/VO to capture and pass related information/involve workflow process.
#Assumption
1) One timecard cannot have daily, weekly, monthly records at the same time. The form will restrict the timecard to one category, which is display daily entry only, weekly entry only, or monthly entry only.
The question is
May I know which part of customization shall use AK Developer or LCT/LDT?, and
Which part of customization shall use OAF/JDeveloper.
Thanks in advanced. I would appreciate for your kind assistance and help
Regards,
Cheng

Icic,
Thanks for your finding. I would like have my next question.
If I would like to have an additional region named "Approvers Region", that similar to the "Approvers Region" that offered by AME-collaborated product.
Is it we need to use OAF method to customize it? or we shall use AK Developer + LTD + OTL Preferences?
I'm not so sure when what is the exact steps should perform when we required to add an new region in OT page.
Thanks in advanced
Regards,
Cheng
Edited by: user13615386 on Nov 1, 2011 3:35 PM

Configuration V/s Customisation

Dear Friends
Can any one tell me what is the difference between Customization & Configuration.
Thanks,
Rams.N

Hello
Both the words go together.
But customization is a step ahead in terms of its nature which could be client specific.
A few examples
Configuration:
-define company code
-define chart of accounts
- Define field status groups
-define account groups
-define document types and so on
Where as examples of customization
- Deciding on number of digits in chart of accounts and customizing the same
- defining new document types
- defining external number ranges and deciding on the logic
- defining the number ranges for customers / vendors
Hope this clears your doubt
Reg
*assign points if useful

How to change the browser title of standard SAP WD4A application - eRecruit

Hi,
I have a requirement to change browser title for standard SAP WD4A application hrrcf_a_candidate_registration. I know this value is used from application description filed.
Current set up is 'Candidate Registration'. (WD Component HRRCF_C_REGISTER_UI)
I tried to use enhancement framework technique and application customization/configuration - but was not successfull.
I do not like the idea of changing the standard SAP object since it might be overwritten in future upgrade. And also I do not prefer to create z* copy of this application as well.
Any ideas how to handle this request? Is dynamic modification of this property possible?
Thanks for your feedback.
Regards,
Igor

Hello,
Did you try to change the description of the service in transaction SICF ?
You can find the Webdynpro services under the tree /default_host/sap/bc/webdynpro/sap/.
Regards,

OC4J_SECURITY is down. SSO: FAILED TO START SSO SERVER

In our Application Server 10.1.2.3.0, OC4J_SECURITY is down.
Log entries in opmn log of OC4J_SECURITY:
09/08/20 11:13:37 Start process
09/08/20 11:13:43 Warning: Error reading transaction-log file (/export/home/oracle/AS_HOME/infra/j2ee/OC4J_SECURITY/persisten
ce/OC4J_SECURITY_default_island_1/transaction.state) for recovery: premature end of file
09/08/20 11:13:43 Forced or abrupt (crash etc) server shutdown detected, starting recovery process...
09/08/20 11:13:43 Recovery completed, 0 connections committed and 0 rolled back...
09/08/20 11:13:47 DAS servlet init enter
09/08/20 11:13:47 oiddas: Release 10.1.2.2.0 Production Started
09/08/20 11:13:51 DAS servlet init exit
09/08/20 11:13:52 SSOLoginServlet.init: Starting up SSO server ...
09/08/20 11:13:52 Initilize NLS utility...
09/08/20 11:13:52 Reading SSO server policy....
09/08/20 11:13:52 SSO: Entered FilePolicyManager constructor ...
09/08/20 11:13:52 SSO: FilePolicyManager: done loading the /export/home/oracle/AS_HOME/infra/sso/conf/policy.properties file
09/08/20 11:13:52 SSO: Leaving FilePolicyManager constructor ...
09/08/20 11:13:52 SSODebug: Done loading the debug file, /export/home/oracle/AS_HOME/infra/sso/log/ssoServer.log
09/08/20 11:13:54 SSO: Initializing the encryption objects failed
09/08/20 11:13:54 oracle.security.sso.server.conf.ConfigurationException: Missing SSO server configuration
09/08/20 11:13:54 at oracle.security.sso.server.conf.DatabaseConfigReader.init(DatabaseConfigReader.java:286)
09/08/20 11:13:54 at oracle.security.sso.server.auth.AuthUtil.init(AuthUtil.java:172)
09/08/20 11:13:54 at oracle.security.sso.server.ui.SSOLoginServlet.init(SSOLoginServlet.java:259)
09/08/20 11:13:54 at javax.servlet.GenericServlet.init(GenericServlet.java:258)
09/08/20 11:13:54 at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2358)
09/08/20 11:13:54 at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4800)
09/08/20 11:13:54 at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4894)
09/08/20 11:13:54 at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1026)
09/08/20 11:13:54 at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:560)
09/08/20 11:13:54 at com.evermind.server.Application.getHttpApplication(Application.java:915)
09/08/20 11:13:54 at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:707)
09/08/20 11:13:54 at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:637)
09/08/20 11:13:54 at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:278)
09/08/20 11:13:54 at com.evermind.server.http.HttpServer.setSites(HttpServer.java:278)
09/08/20 11:13:54 at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:179)
09/08/20 11:13:54 at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2435)
09/08/20 11:13:54 at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1592)
09/08/20 11:13:54 at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92)
09/08/20 11:13:54 at java.lang.Thread.run(Thread.java:534)
09/08/20 11:13:54 SSO: FAILED TO START SSO SERVER!
Log entries of <Infra_home>/sso/log/ssoServer.log
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Done loading Policy Configurations
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Login Page Value: /sso/jsp/login.jsp
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Change password Page location: /sso/jsp/password.jsp
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Wireless Login Page location: /wirelesssso/wirelesslogin.jsp
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Wireless Change password Page location: /wirelesssso/wirelesscpwd.jsp
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Calling Initialization Methods ...
Thu Aug 20 11:13:52 AST 2009 [INFO] Orion Launcher Entered DBConnectionPool.init method ...
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Repository API returned - DB conn string: ldap://webportaldev.bh.zain.com
:389/ptldev,cn=oraclecontext
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Setting max number of connections to 150 in the DB cache pool
Thu Aug 20 11:13:52 AST 2009 [DEBUG] Orion Launcher Setting minimum number of connections to 5 in the DB cache pool
Thu Aug 20 11:13:53 AST 2009 [INFO] Orion Launcher Leaving DBConnectionPool.init method ...
Thu Aug 20 11:13:53 AST 2009 [INFO] Orion Launcher Entered DBConnectionPool.getConnection method ...
Thu Aug 20 11:13:53 AST 2009 [INFO] Orion Launcher Leaving DBConnectionPool.getConnection method ...
Thu Aug 20 11:13:54 AST 2009 [DEBUG] Orion Launcher DatabaseConfigReader: Setting LDAP configurations
Thu Aug 20 11:13:54 AST 2009 [DEBUG] Orion Launcher DatabaseConfigReader: Setting Customizable configurations
Thu Aug 20 11:13:54 AST 2009 [DEBUG] Orion Launcher SQL Exception received: java.sql.SQLException: ORA-04063: package body "O
RASSO.WWSSO_LS_PRIVATE" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
Thu Aug 20 11:13:54 AST 2009 [DEBUG] Orion Launcher DBConnectionPool: Checking for DB connection errors..
Thu Aug 20 11:13:54 AST 2009 [ERROR] Orion Launcher SSO Server initialization failed. Check the DB availability and restart S
SO Server
Thu Aug 20 11:13:54 AST 2009 [ERROR] Orion Launcher Initializing the encryption/decryption objects failed
oracle.security.sso.server.conf.ConfigurationException: Missing SSO server configuration
at oracle.security.sso.server.conf.DatabaseConfigReader.init(DatabaseConfigReader.java:286)
at oracle.security.sso.server.auth.AuthUtil.init(AuthUtil.java:172)
at oracle.security.sso.server.ui.SSOLoginServlet.init(SSOLoginServlet.java:259)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2358)
at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4800)
at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4894)
at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1026)
at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:560)
at com.evermind.server.Application.getHttpApplication(Application.java:915)
at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:707)
at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:637)
at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:278)
at com.evermind.server.http.HttpServer.setSites(HttpServer.java:278)
at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:179)
at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2435) at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1592)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92)
at java.lang.Thread.run(Thread.java:534)
Can anyone help us to fix this issue?

Hi,
Apparently, there is a problem in package “*wwsso_ls_private*”. I got below error while trying to compile this package. When I was trying to compile ORASSO.WWSSO_LS_PRIVATE, I got the below errors about parameters
SQL> alter package ORASSO.WWSSO_LS_PRIVATE compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY ORASSO.WWSSO_LS_PRIVATE:
LINE/COL ERROR
484/4 PL/SQL: SQL Statement ignored
484/16 PL/SQL: ORA-00947: not enough values
628/6 PL/SQL: SQL Statement ignored
628/20 PL/SQL: ORA-00904: "LSCI": invalid identifier
681/4 PL/SQL: SQL Statement ignored
684/10 PL/SQL: ORA-00904: "LSCONFIG": invalid identifier
Cause:
The possible cause this issue is some problem that occured when
applying the latest patchset. The patchset does include updates of ODS and ORASSO schemas and their objects. If parts of objects were not updated with the new version and the old version is still in DB, errors may occur (for example when I was trying to compile ORASSO.WWSSO_LS_PRIVATE I got the errors
about parameters, which indicate version mismatch).
To fix this problem, I have re defined the problem giving package.
This package wwsso_ls_private is defined in
$ORACLE_HOME/sso/admin/plsql/sso/ssolsprv.pks
Solution:
I have fixed the problem by following the below steps.
1. Login sqlplus as orasso user of MR
2. Recreate the view wwsso_ls_configuration_info$ by issuing the below DDL statement.
SQL> CREATE OR replace VIEW wwsso_ls_configuration_info$ OF ls_config_type WITH object oid(config_name) as select * from wwsso_ls_configuration_info_t;
3. Now compile the problem giving package.
SQL> alter package wwsso_ls_private compile body;
Compilation of this package was done without any error.
4. Now all the OC4J container including OC4J_SECURITY in our Infra tier are up and running.
-Thanks,
Padmanaban G

ISF/javascript code doesn't work for non-English RequestCenter proile

ISF/javascript code doesn't work for non-English RequestCenter proile
Hello,
I am not sure if i posted the same question before also. We have some customers who have set thier language profile in newScale requestcenter to French. However, all the javascript customizations configured on the service forms do not function for 'French' as a Langauge preference. Has anyone encountered the similar issue before and can anyone please suggest a solution for it?
Thanks,
Mihir

we had a similar issue a while back where the Approval button was not working in Spanish, needed a fix from nS for it
The way to fix this would be to locate the language XML file, override the French caption with Submit and on onLoad write a global JS that would write the button label again (not so sure about this)
But really its an major defect and they should be able to fix it.

Customization -configuration

Similar Messages

Maybe you are looking for