|
Sap questions and answers for specific problem |
Q&A Database
How to move SAP servers to a virtual machine ?
From irrshaad :
We are planning to move our SAP servers to a virtual machine (VM). and I have some questions related this, - what is time required to move the SAP system to Virtual machine? - whether down time is needed for SAP servers? - Whether SAP system which is running on windows and SAP system which is running on Linux can be moved? |
Answer from Robert :
Linux and Windows will both work on VM, we have two SAP environments one on each. The Hosts wil have to be different though. i.e. you have your Windows VMs on a Windows Host and your Linux VMs on a Linux Host.
If you are simply deattaching and presenting your storage from your current physical server to a VM server then this is relatively quick and avoids the need for a 5 to 10 outage to export and import databses. Clearly you should run through this in a test system to begin with, get your process and timings confirmed, best approach would be to take a copy of your PRD database into test and rehearse the move - that way you should get exact timings. |
|
How to create a recurring document or a sample document.
Example post Prepaid Insurance every month. In order to post the Recurring entry you can follow the following steps: Step1. Tcode FKMT --> here you can create a Assignment model by Debiting your Expenses and Crediting your prepaid Account. (this is just a Templet so for and positing has not taken place) step 2. Tcode FBD1 --> here you could recall the assignment model, specify the respective period of posting Example Start with 1st Nov XX end with 30 Nov XX for a period and specify the batch name. Step 3. Tcode SM35 --> here you look for the batch name which you saved while you did step 2 and run the batch. Step 4. Tcode FB03 --> see the postings if that has posted correctly by debiting the expenses account ( actual monthly figure not the yearly figure and credited the Prepaid account) If you follow these steps, it should work as there is no configurations
for Recurring entry, but for Manual Accruals there is config.
Example set up recurring entries on weekly and fortnightly basis, do we have the option to set up Run Frequency on week and fortnight, as I could see only monthly. Step 1. Use transaction OBC1 and define the run schedule for e.g. TEST. Step 2. Use transaction OBC2 and maintain run dates you want for the scedule defined above. Step 3. Use transaction FBD1 to create recurring document and enter the Run Schedule you defined in step 1. |
How to set up commission for saleman?
|
For creating commission agent, follow below steps. 1) Establish Partner Functions for the Commissionee(s) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 2) Assign the Partner Functions to Partner Procedures Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 3) Create a Partner Procedure for the Commissionees Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 4) Create New Customer Account Group(s) for Commission Agents Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER Transaction Code: OVT0 5) Assign the Partner Functions to the Customer Account Group(s) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT Transaction Code: VOPA 6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions Transaction Code: VOPA 7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS Transaction Code: VOPA 8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent) Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY Transaction Code: SE11 9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion). 13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction Code: OV24 14) Create Condition Tables (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction Code: V/03 15) Create an access sequence containing the new tables (Client Independent) Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES Transaction Code: V/07 16) Create a new condition type Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES Transaction Code: V/06 17) Add the Condition Type to the Pricing Procedure Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES Transaction Code: V/08 11) Create Commsission Report ZZCOMMISSION (Client Independent) Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR Transaction Code: SE38 |
1-5 of 5