Maintain requirements for TOR

Hi experts, pls help solve as below. Thx.
Q1: In OVB8, how to change SyRoutine from 1 to 103 as the field is grey?
Q2: How can sales orders capture the relevant data after maintaining requirements for TOR? In other words, any other configurations if this maintainence is applied to sales orders?
Background info: Try to suppress MRP in case of credit block (MTO scenario).

Maybe I need to be a bit more specific on the requirement.
Strategy group = 40 with requirement type VSF (ind. req.) and KSV (Cust. req.).
My client works in 2 distribution channels:
- For the standard sales (DC 01) the confirmed quantities should reduce the independent requirement quantity, so KSV is the correct requirement type (it shows by default on the sales item).
- For aftersales (DC 04) the independent requirement should not be reduced with the SO quantity and not KSV is wanted, but 011.
In my opinion it should be possible to override the default KSV with 011 in case the distribution channel is 04. The SPRO activity below looks suitable:
Alternative could be maybe to change progam MV45AFZZ / user exit USEREXIT_SAVE_DOCUMENT_PREPARE.
Please advise.

Similar Messages

What are the infotypes required for maintaining benefits....

Hi
Please help ...
What are the ingotypes required for maintaing benefits....

Hi Srikanth,
Please find below the list of Infotypes required for maintaining benefits:
1. General Benefits Information (Infotype 0171)
2. Adjustment Reasons (Infotype 0378)
3. Health Plans (Infotype 0167)
4. Insurance Plans (Infotype 0168)
5. Savings Plans (Infotype 0169)
6. Flexible Spending Account (Infotype 0170)
7. Miscellaneous Plans (Infotype 0377)
8. Family/Related Person (Infotype 0021)
There are also other benefits infotypes e.g. Stock Purchase Plans (Infotype 0379), Credit Plans (Infotype 0236) and many COBRA and retirement plan infotypes but these are used based on the company requirement.
I hope this helps.
Regards,
Anand Jalan
Edited by: Anand Jalan on Jan 6, 2010 9:50 PM
Edited by: Anand Jalan on Jan 6, 2010 9:52 PM

How to maintain year of experience required for a position?

Hi All,
There is a very requirement for a position like "3 years of experience as Executive" I dont know how to maintain this requirement in SAP. Right now we have created a qualification named "Executive Experience" with a time scale assigned to it with a validity period of one year so HR dept must change the scale evey year. It works but it's not best practice. I know if there is a way we can use employee past and current work history to determine the level of experience and also how to define this requirement in position profile.

Hi Dilek,
I maintained all those thing. But i have to do the selection process on the basis of position with year of experience. While doing the selection process via Position or Qualification its picking up the exact applicant. I created a career as 3 years as you said so that the minimum year of experience for that position is 3 years. Then where i can give the year of experience for the applicant? Even though i maintained the previous employer details as 2 years the system is picking up the applicant. Logic wise how to do this?
Please help me to sort out this problem.
Thanks in advance,
Magesh S.

How to maintain experience requirement for a position

Hi All,
There is a very common requirement for a position like "5 years of experience in management level" I dont know how to maintain this requirement in SAP. right now we have created a qualification named "Management Experience" with a time scale assigned to it with a validity period of one year so HR dept must change the scale evey year. It works but it's not best practice. I know if there is a way we can use employee past and current work history to determine the level of experience and also how to define this requirement in position profile.
Thanks in advance,
Shahin

I guess it will be SU12 Transaction.
Thanks
Seshu

What are the settings required for QM in procurement

Hi Team,
What are the settings required for QM in procurement. I have set indicator for QM in procurement in QM view in material master.
I am not clear about following fields to be maintained in QM view.
QM Control Key
Certificate type
Target QM system
Tech. delivery terms Indicator.
Please suggest me in which case to be used this fiels. Is it relivant to Quality Certificates.
Thanks

Hi,
All meaning are
QM Control Key :
If you activate the indicator for QM in procurement in the material master record at the client level, you must also store a control key at the plant level for quality management in procurement.
Certificate type :
Certificate types applies to the Certificate processing in procurement & Certificate creation
Target QM system :
whether the vendor's verified QM system, according to vendor master record or quality info-record (for a combination of vendor/material) meets the requirements for QM systems as specified in the material master
- If you activate the indicator for QM in procurement in the material master record at the client level, you must also store a control key at the plant level for quality management in procurement. If you want Procurment control then accordingly define Control Key.
- If you want Vendor's perticular certificate for Material then you have to define Certificate type.
Also, you have to maintain Material, Vendor's Info record at plant level.
Thanks,
JM

List of Manual Setup required for iSetup to work

Hi All,
This is Mugunthan from iSetup development. Based on my interaction with customers and Oracle functional experts, I had documented list of manual setups that are required for smooth loading of selection sets. I am sharing the same. Please let me know if I anyone had to enter some manual setup while using iSetup.
Understanding iSetup
iSetup is a tool to migrate and report on your configuration data. Various engineering teams from Oracle develop the APIs/Programs, which migrates the data across EBS instances. Hence all your data is validated for all business cases and data consistency is guarantied. It requires good amount of setup functional knowledge and bit of technical knowledge to use this tool.
Prerequisite setup for Instance Mapping to work
· ATG patch set level should be same across all EBS instances.
· Copy DBC files of each other EBS instances participating in migration under $FND_SECURE directory (refer note below for details).
· Edit sqlnet.ora to allow connection between DB instacnes(tcp.invited_nodes=(<source>,<central>))
· Make sure that same user name with iSetup responsibility exists in all EBS instances participating in migration.
Note:- iSetup tool is capable of connecting to multiple EBS instances. To do so, it uses dbc file information available under $FND_SECURE directory. Let us consider three instances A, B & C, where A is central instance, B is source instance and C is target instances. After copying the dbc file on all nodes, $FND_SECURE directory would look like this on each machine.
A => A.dbc, B.dbc, C.dbc
B => A.dbc, B.dbc
C => A.dbc, C.dbc
Prerequisite for registering Interface and creating Custom Selection Set
iSetup super role is mandatory to register and create custom selection set. It is not sufficient if you register API on central/source instance alone. You must register the API on all instances participating in migration/reporting.
Understanding how to access/share extracts across instances
Sharing iSetup artifacts
· Only the exact same user can access extracts, transforms, or reports across different instances.
· The “Download” capability offers a way to share extracts, transforms, and loads.
Implications for Extract/Load Management
· Option 1: Same owner across all instances
· Option 2: Same owner in Dev, Test, UAT, etc – but not Production
o Extract/Load operations in non-Production instances
o Once thoroughly tested and ready to load into Production, download to desktop and upload into Production
· Option 3: Download and upload into each instance
Security Considerations
· iSetup does not use SSH to connect between instances. It uses Concurrent Manager framework to lunch concurrent programs on source and target instances.
· iSetup does not write password to any files or tables.
· It uses JDBC connectivity obtained through standard AOL security layer
Common Incorrect Setups
· Failure to complete/verify all of the steps in “Mapping instances”
· DBC file should be copied again if EBS instance has been refreshed or autoconfig is run.
· Custom interfaces should be registered in all EBS instances. Registering it on Central/Source is not sufficient.
· Standard Concurrent Manager should up for picking up iSetup concurrent requests.
· iSetup financial and SCM modules are supported from 12.0.4 onwards.
· iSetup is not certified on RAC. However, you may still work with iSetup if you could copy the DBC file on all nodes with the same name as it had been registered through Instance Mapping screen.
Installed Languages
iSetup has limitations where it cannot Load or Report if the number and type of installed languages and DB Charset are different between Central, Source and Target instances. If your case is so, there is a workaround. Download the extract zip file to desktop and unzip it. Edit AZ_Prevalidator_1.xml to match your target instance language and DB Charset. Zip it back and upload to iSetup repository. Now, you would be able to load to target instance. You must ensure that this would not corrupt data in DB. This is considered as customization and any data issue coming out this modification is not supported.
Custom Applications
Application data is the prerequisite for the most of the Application Object Library setups such as Menus, Responsibility, and Concurrent programs. iSetup does not migrate Custom Applications as of now. So, if you have created any custom application on source instance, please manually create them on the target instance before moving Application Object Library (AOL) data.
General Foundation Selection Set
Setup objects in General foundation selection set supports filtering i.e. ability to extract specific setups. Since most of the AOL setup data such as Menus, Responsibilities and Request Groups are shipped by Oracle itself, it does not make sense to migrate all of them to target instance since they would be available on target instance. Hence, it is strongly recommended to extract only those setup objects, which are edited/added, by you to target instance. This improves the performance. iSetup uses FNDLOAD (seed data loader) to migrate most of the AOL Setups. The default behavior of FNDLOAD is given below.
Case 1 – Shipped by Oracle (Seed Data)
FNDLOAD checks last_update_date and last_updated_by columns to update a record. If it is shipped by Oracle, the default owner of the record would be Oracle and it would skip these records, which are identical. So, it won’t change last_update_by or last_updated_date columns.
Case 2 – Shipped by Oracle and customized by you
If a record were customized in source instance, then it would update the record based on last_update_date column. If the last_update_date in the target were more recent, then FNDLOAD would not update the record. So, it won’t change last_update_by column. Otherwise, it would update the records with user who customized the records in source instance.
Case 3 – Created and maintained by customers
If a record were newly added/edited in source instance by you, then it would update the record based on last_update_date column. If the last_update_date of the record in the target were more recent, then FNDLOAD would not update the record. So, it won’t change last_update_by column. Otherwise, it would update the records with user who customized the records in source instance.
Profiles
HR: Business Group => Set the name of the Business Group for which you would like to extract data from source instance. After loading Business Group onto the target instance, make sure that this profile option is set appropriately.
HR: Security Profile => Set the name of the Business Group for which you would like to extract data from source instance. After loading Business Group onto the target instance, make sure that this profile option is set appropriately.
MO: Operating Unit => Set the Operating Unit name for which you would like to extract data from source instance. After loading Operating Unit onto the target instance, make sure that this profile option is set if required.
Navigation path to do the above setup:
System Administrator -> Profile -> System.
Query for the above profiles and set the values accordingly.
Descriptive & Key Flex Fields
You must compile and freeze the flex field values before extracting using iSetup.
Otherwise, it would result in partial migration of data. Please verify that all the data been extracted by reporting on your extract before loading to ensure data consistency.
You can load the KFF/DFF data to target instance even the structures in both source as well as target instances are different only in the below cases.
Case 1:
Source => Loc1 (Mandate), Loc2 (Mandate), Loc3, and Loc4
Target=> Loc1, Loc2, Loc3 (Mandate), Loc4, Loc5 and Loc6
If you provide values for Loc1 (Mandate), Loc2 (Mandate), Loc3, Loc4, then locations will be loaded to target instance without any issue. If you do not provide value for Loc3, then API will fail, as Loc3 is a mandatory field.
Case 2:
Source => Loc1 (Mandate), Loc2 (Mandate), Loc3, and Loc4
Target=> Loc1 (Mandate), Loc2
If you provide values for Loc1 (Mandate), Loc2 (Mandate), Loc3 and Loc4 and load data to target instance, API will fail as Loc3 and Loc4 are not there in target instance.
It is always recommended that KFF/DFF structure should be same for both source as well as target instances.
Concurrent Programs and Request Groups
Concurrent program API migrates the program definition(Definition + Parameters + Executable) only. It does not migrate physical executable files under APPL_TOP. Please use custom solution to migrate executable files. Load Concurrent Programs prior to loading Request Groups. Otherwise, associated concurrent program meta-data will not be moved even through the Request Group extract contains associated Concurrent Program definition.
Locations - Geographies
If you have any custom Geographies, iSetup does not have any API to migrate this setup. Enter them manually before loading Locations API.
Currencies Types
iSetup does not have API to migrate Currency types. Enter them manually on target instance after loading Currency API.
GL Fiscal Super user--> setup--> Currencies --> rates -- > types
Associating an Employee details to an User
The extract process does not capture employee details associated with users. So, after loading the employee data successfully on the target instance, you have to configure them again on target instance.
Accounting Setup
Make sure that all Accounting Setups that you wish to migrate are in status “Complete”. In progress or not-completed Accounting Setups would not be migrated successfully.
Note: Currently iSetup does not migrate Sub-Ledger Accounting methods (SLA). Oracle supports some default SLA methods such as Standard Accrual and Standard Cash. You may make use of these two. If you want to use your own SLA method then you need to manually create it on target instances because iSetup does not have API to migrate SLA. If a Primary Ledger associated with Secondary Ledgers using different Chart of Accounts, then mapping rules should be defined in the target instance manually. Mapping rule name should match with XML tag “SlCoaMappingName”. After that you would be able to load Accounting Setup to target instance.
Organization API - Product Foundation Selection Set
All Organizations which are defined in HR module will be extracted by this API. This API will not extract Inventory Organization, Business Group. To migrate Inventory Organization, you have to use Inventory Organization API under Discrete Mfg. and Distribution Selection Set. To extract Business Group, you should use Business Group API.
Inventory Organization API - Discrete Mfg & Distribution Selection Set
Inventory Organization API will extract Inventory Organization information only. You should use Inventory Parameters API to move parameters such as Accounting Information. Inventory Organization API Supports Update which means that you can update existing header level attributes of Inventory Organization on the target instance. Inventory Parameters API does not support update. To update Inventory Parameters, use Inventory Parameters Update API.
We have a known issue where Inventory Organization API migrates non process enabled organization only. If your inventory organization is process enabled, then you can migrate them by a simple workaround. Download the extract zip file to desktop and unzip it. Navigate to Organization XML and edit the XML tag <ProcessEnabledFlag>Y</ProcessEnabledFlag> to <ProcessEnabledFlag>N</ProcessEnabledFlag>. Zip it back the extract and upload to target instance. You can load the extract now. After successful completion of load, you can manually enable the flag through Form UI. We are working on this issue and update you once patch is released to metalink.
Freight Carriers API - Product Foundation Selection Set
Freight Carriers API in Product Foundation selection set requires Inventory Organization and Organization Parameters as prerequisite setup. These two APIs are available under Discrete Mfg. and Distribution Selection Set. Also,Freight Carriers API is available under Discrete Mfg and Distribution Selection Set with name Carriers, Methods, Carrier-ModeServ,Carrier-Org. So, use Discrete Mfg selection set to load Freight Carriers. In next rollup release Freight Carriers API would be removed from Product Foundation Selection Set.
Organization Structure Selection Set
It is highly recommended to set filter and extract and load data related to one Business Group at a time. For example, setup objects such as Locations, Legal Entities,Operating Units,Organizations and Organization Structure Versions support filter by Business Group. So, set the filter for a specific Business Group and then extract and load the data to target instance.
List of mandatory iSetup Fwk patches*
8352532:R12.AZ.A - 1OFF:12.0.6: Ignore invalid Java identifier or Unicode identifier characters from the extracted data
8424285:R12.AZ.A - 1OFF:12.0.6:Framework Support to validate records from details to master during load
7608712:R12.AZ.A - 1OFF:12.0.4:ISETUP DOES NOT MIGRATE SYSTEM PROFILE VALUES
List of mandatory API/functional patches*
8441573:R12.FND.A - 1OFF:12.0.4: FNDLOAD DOWNLOAD COMMAND IS INSERTING EXTRA SPACE AFTER A NEWLINE CHARACTER
7413966:R12.PER.A - MIGRATION ISSUES
8445446:R12.GL.A - Consolidated Patch for iSetup Fixes
7502698:R12.GL.A - Not able to Load Accounting Setup API Data to target instance.
Appendix_
How to read logs
· Logs are very important to diagnose and troubleshoot iSetup issues. Logs contain both functional and technical errors.
· To find the log, navigate to View Detail screens of Extracts/ Transforms/Loads/Standard/Comparison Reports and click on View Log button to view the log.
· Generic Loader (FNDLOAD or Seed data loader) logs are not printed as a part of main log. To view actual log, you have to take the request_id specified in the concurrent log and search for the same in Forms Request Search Window in the instance where the request was launched.
· Functional errors are mainly due to
o Missing prerequisite data – You did not load one more perquisite API before loading the current API. Example, trying to load “Accounting Setup” without loading “Chart of Accounts” would result in this kind of error.
o Business validation failure – Setup is incorrect as per business rule. Example, Start data cannot be greater than end date.
o API does not support Update Records – If the there is a matching record in the target instance and If the API does not support update, then you would get this kind of errors.
o You unselected Update Records while launching load - If the there is a matching record in the target instance and If you do not select Update Records, then you would get this kind of errors.
Example – business validation failure
o VONAME = Branches PLSQL; KEY = BANKNAME = 'AIBC‘
o BRANCHNAME = 'AIBC'
o EXCEPTION = Please provide a unique combination of bank number, bank branch number, and country combination. The 020, 26042, KA combination already exists.
Example – business validation failure
o Tokens: VONAME = Banks PLSQL
o BANKNAME = 'OLD_ROYAL BANK OF MY INDIA'
o EXCEPTION = End date cannot be earlier than the start date
Example – missing prerequisite data.
o VONAME = Operating Unit; KEY = Name = 'CAN OU'
o Group Name = 'Setup Business Group'
o ; EXCEPTION = Message not found. Application: PER, Message Name: HR_ORG_SOB_NOT_FOUND (Set of books not found for ‘Setup Business Group’)
Example – technical or fwk error
o OAException: System Error: Procedure at Step 40
o Cause: The procedure has created an error at Step 40.
o Action: Contact your system administrator quoting the procedure and Step 40.
Example – technical or fwk error
o Number of installed languages on source and target does not match.
Edited by: Mugunthan on Apr 24, 2009 2:45 PM
Edited by: Mugunthan on Apr 29, 2009 10:31 AM
Edited by: Mugunthan on Apr 30, 2009 10:15 AM
Edited by: Mugunthan on Apr 30, 2009 1:22 PM
Edited by: Mugunthan on Apr 30, 2009 1:28 PM
Edited by: Mugunthan on May 13, 2009 1:01 PM

Mugunthan
Yes we have applied 11i.AZ.H.2. I am getting several errors still that we trying to resolve
One of them is
===========>>>
Uploading snapshot to central instance failed, with 3 different messages
Error: An invalid status '-1' was passed to fnd_concurrent.set_completion_status. The valid statuses are: 'NORMAL', 'WARNING', 'ERROR'FND at oracle.apps.az.r12.util.XmlTransmorpher.<init>(XmlTransmorpher.java:301)
 at oracle.apps.az.r12.extractor.cpserver.APIExtractor.insertGenericSelectionSet(APIExtractor.java:231)
please assist.
regards
girish

Difference between defining segment and maintaining segment for GL items

Hello All,
Can someone tell me the difference between 'Defining a Segment' (in enterprise structure) and 'Maintaining Segment for general ledger Items' (tcode FQ0300) and when is the later used?

Hi,
Segment reporting is part of functional reporting in sap. Segment reporting is required as per International Accounting Standard 14 for listed companies thats why it is defined in Enterprise structure .
Segment is maintained in profit
center master data from where it is derived, When you post to a GL account containing segment it gets posted to profit center. This is the basis purpose of maintaining segment at Gl account level. Segment reporting is gradually being replaced by business area. This is for you information.
Regards

How to create a maintainance view for a table.

Hi All,
Can anyone explain me how do we create a maintainance view for a table?
Also, what access is required to create the view.
Is it true that for SAP tables we cannot create a maintainance view?
Appreciate any help on this.

Hi
Can anyone explain me how do we create a maintainance view for a table?

You can use the SE11 menu option 'Utilities-->Table Maintenance Generator' or you can use transaction SE54.
also check
http://help.sap.com/saphelp_nw04/helpdata/en/38/81c1351181b73fe10000009b38f839/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/38/81c1351181b73fe10000009b38f839/frameset.htm
Regards
krishna
Note: Award Points if helpful. Thanks

Why is Domain required for an identity in the FIM Service?

I have a scenario where FIM is managing identity, but not all identities have an Active Directory account. I have a flag in the FIM Portal (Service) that indicates if a particular
user is entitled to an AD account or not. My provisioning setup adds or removes the AD account as appropriate. To support FIM Portal activities for those that do have AD accounts, I populate AccountName, Domain, and ObjectSID in the FIM Service from their
corresponding attributes in AD.
What I have noticed is that it does not seem possible to null out or delete the Domain attribute for a user in the FIM Service. I can delete the attributes for both AccountName
and ObjectSID without issues.
When attempting to remove the Domain attribute for a user I get the following in the event logs:
Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Procedure or function 'GetDomainConfigurationIdentifiersFromDomain'
expects parameter '@domainName', which was not supplied.
I assume that something internal to the FIM Service is trying to do some magic with validating the domain name and the domain configuration. I did found a post saying, “Yeah,
you have to populate Domain”:
http://social.technet.microsoft.com/Forums/en-US/f207caa9-3a6f-4f2d-8461-a83777280803/fim-service-ma-export-failedmodificationviawebservices-error?forum=ilm2
My question is why is Domain required for a user? It is obviously needed for users that have AD accounts an must authenticate with the Portal, but in the case where a user
does not have an account (and therefore does not have a domain), it feels odd to store the incorrect data for the user. It also looks weird when you bring up list of users in the portal and see domain values for users that do not have accounts. In this particular
case, the client has many domains and does have the Domain and AccountName attributes displayed on the user search results page.

Hi Henry,
Using another domain attribute and workflow to maintain the actual Domain and DomainConfiguration is a good suggestion, thanks.
My original question still stands however... Why is Domain required in the FIM Service?
It is sounding like the answer is "It is not really required on it's own, but there is an internal process that requires it if there is a value for DomainContext set (and there is some magic that sets DomainContext, so you have to manually clear it.)"
Since DomainContext is automatically set when a client writes a value to Domain. I would suggest that it is a bug that DomainContext is not automatically cleared when Domain is cleared.
I poked around a bit and the bug can be fixed by changing the stored procedure definition to allow null parameters. In the FIM Service database the stored procedure [fim].[GetDomainConfigurationIdentifiersFromDomain] has a parameter declaration of "@domainName
NVARCHAR(448)". If this is changed to "@domainName NVARCHAR(448) = null" the problem appears to be solved.
Making this change would of course be totally unsupported, but perhaps it can be included in a future product update.
For now I will use Henry's workaround, or just live with potential out of date Domain data.
Thanks

Transfer of Requirements for Return Orders

Hi,
Please I need help on TOR management with Return Orders in SD.
I've already red all the threads realted to TOR and ATP but I couldn't find a solution. As we know TOR is dependent on the following data: reqts type, reqts class, checking group and schedule line category.
The reqts type and class are determined in the strategy group (material master - MRP3).
Now if I switch on Transfer of Requirements for Returns, at Schedule Line level and Reqts Class level, the result is that I can see requirements related to Returns in the availability check overview of Sales Orders (ATP count) but if I check in the requirements list (i.e. transaction MD04) these requirements related to Returns are not recorded. Why?
And also another point please: requirements generated from Return Orders, into ATP count are considered as normal Sales Orders (negative sign, reducing ATP quantity, when it should be the contrary because a goods receipt is expected).
Can you help me please on these 2 points (perhaps something related with Sales Document Category)?
Thank you very much
Kind Regards
AP

I practically did a sample order / returns order to see your requirements and these are my observations
a)
If you create a standard sales order, then the availability check registers a minus sign with stock required in Rec./reqd qty field.
Once you save the sales order, this is not seen again as the total quantity is reduced by sales order quantity.
It was indicating a minus sign when you created a returns order because you checked the Transfer of requirements and availability check indicators in schedule line category.
It was simulating a requirement as you checked the indicators in schedule line category.
If you create returns order with standard DN (i.e. Transfer of requirements and availability check indicators are not checked), then you would not see any requirement for stock i.e. you don't see any new entry in availability overview screen.
b)
You are not seeing returned quantities in MD04 because of Movement types. This has nothing to do with Transfer of requirements.
Schedule line DN uses movement type 651.
Using movement type 651, you post returns from a customer with returns delivery to blocked stock returns.
The blocked stock returns are are neither valuated nor part of "unrestricted-use" stock.
Hence you are not seeing the returned stock in your available stock.
If you click the magnifying glass on total stock i.e. top line of your stock/requirements list (transaction MD04), you could see the returned quantity in 'Returns field'.
If you want to post returns from a customer with returns delivery directly to the valuated stock, you could use the following movement types in schedule line category.
653 Returns from customer to unrestricted-use stock
655 Returns from customer to stock in quality inspection
With these movement types, you could see returned quantities in stock/requirements list.

Pdf doc is required for B2C CRM 2007 WEB SHOP

Hello Experts,
We have a scenario where (pdf doc ) is required for b2c Header level and tem level in CRM 2007 web channel.
we have set up a product and product catalog and maintained a PDF document in the HEADER AREA--
Documents Tab--BDS_PDF folder.
After intial replication Documents was published in the following path
*catalog/DE DE161EE3D35DAAF19F1E000C29D94525.pdf *
we are able to find images and pdf in the index server but unable to see the same in the web shop.
Did I miss some thing ? Do I need to do any other settings in XCM or in JSP?
Thanks in advance
Namitha Verma

Hello namitha Verma
I am facing the same problem, are you able solve the problem kindly let me know .
Regards
Kiran Posanapalli

What is setting required for Price Contol do the optional entery in master.

Hi SAP EXPERT,
What is setting required for Price Contol do the optional entery in Material master ?
Regards
Mahendra
Edited by: MAHENDRA NAVALE on Aug 27, 2011 2:23 PM

HI
In general in the material master record you can, hide display or optional for a field, but there are certain feilds should be mandatory for material creation,like base unit of measure,material description,and price contro,l valuation price,valuation class,without this you cannot create a purchase order.
If you dont want to the price control means go for mateial type non valuated material NLAG. because the price control is mainly linked with the material valuation. based on the the price control the price difference will post either sock account or price difference account.
Goto>MM>LOGISTICS GENERAL>MATERIAL MASTER>FEILD SELECTION >ASSIGN FEILD SELECTION TO FEILD SELECTIN GROUPS(OMSR) >CHECK YOUR FEILD REFERENCE FOR PRICE CONTROL (MBEW-VPRSV) FEILD REFERNCE GROUP IS 32* > AND GOTO MAINTAIN FEILD REFERENCE FOR DATA SCREENS (OMS9) >ENTER YOUR FEILD SELECTIN GROUP 32 (PRICE CONTROL )AND CHOOSE MM01 MAKE IT FROM REQUIRED TO OPTIONAL.
Thanks
Edited by: Nijamudeen**MM on Aug 29, 2011 10:19 AM

Requirements for lead management system in sap sd

hii
can we maintain lead management system in sap sd module..what are the requirements for lead management system.

no

Config required for Imports in IMG

Dear All,
Please provide me with some information related to the configuration required for the imports in IMG.
What are the settings to be made in Foriegn Trade/Customs.
Regards,
Venkat.

Hi
following is a process for import PO
1)Create Vendor and give Order Currency(USD,JPY Etc) in XK01.
2)Create Material Master and give appropriate Description Because Users shoud Identify Correct Mtrl Or Activate Split valuation.
3)Create Import Purchase order for Import Vendor ( U can create separete Document type and Purchasing group.but not necessary )
4)Mention Duty rates (CVD,Customs,Cess on CVD,cess on Customs,HSC on CVD,HSC on Customs and ADC) and Don't forget to mention Custom Vendor In Duty rates condition type.
5)MIRO Customs Invoice,U can Invoice in Vendor Currency as well as Indian Currency.
6)Recieve the Material Through MIGO,If you Currectly maintaining Customizing of Excise Duties at the Time of MIGO u can take credit for CVD,Cess on CVD,HSC on CVD and ADC and rest of all add to ur material cost.
7)In MIGO u can Capture the Excise invoice and in J1IEX post the Excise invoice.
8)After Recieving the goods and Payment to the Customs raise a Invoice for Main Vendor.
summary can be like this
U need to have seperate pricing procedure for import--IMG
spro>Materials Management>Purchasing>Conditions>Define Price Determination Process-->Define Calculation Schema
maintain relation betn. pricing schema and schema group -- IMG
spro>Materials Management>Purchasing>Conditions>Define Price Determination Process-->Define Schema Determination
Assign schema group to vendor master in Vm creation or in XK02--( Master data activity
based on schema group assigned to vendor pricing procedure will automaticaly picked up in PO
Rest is a normal process
Vishal...

What all the prerequisites required for Combined Delivery &Invoice Process

Dear Guru's
Can you please educate me what all the prerequisites required for Combined Delivery Process(VL10A / VL10C) and Combined Invoice Process?
Regards,
Varma

Hi ,
For combined delivery you have to make some settings
In the customer master XD01/VD01 in the shipping tab you have to check the ORDER COMBINATION in the SHIPPING TAB
In the COPY CONTROLS from Order to Delivery in VTAL at the Header you have to maintain the COMBINATION REQUIREMENT as 051
And also the data like
INCO TERMS,
SHIP TO PARTY
DELIVERY DATE
ROUTE
SHIPPING POINT
should be same for all the Orders
To combine the Deliveries into Invoice
you have to maintain the copy controls from DELIVERY TO BILLING in VTFL at the item level as 003
And also certain data like
PAYMENT TERMS
PAYER
BILLING DATE
ACTUAL GI DATE
INCO TERMS
should be same for all the deliveries
Please revert if you need any more
regards,
santosh

Maintain requirements for TOR

Similar Messages

Maybe you are looking for