Account determination screen shot

Hi sd gurus,
can any one plz send me the screen shots for acount determination screen shots in sd point and rebates screen shots.

Hi
Pls go to t.code: VKOA - to create Revenue account determination, and
Application: V
Condition type: KOFI & KOFK
Chart of accounts: INT
Sales organization: 1000,
Copy all the enteries in the following seletion and copy to your company code for all the five tables.
Reward if it helps
Regards
Prasanna R

Similar Messages

  • Version 9.1 - Advanced GL Account determination - WIP Mapping Tab

    Dear community,
    Does anybody have an idea / documentation with respect to the functionality under the WIP Mapping tab in Advanced GL Account determination screen of version 9.1?
    Consolidate from accounts can be mapped to Consolidate To accounts under that Menu path.
    Even when a production order is closed with Variances and with the document setting (Production Order > Posting Schemas for Manufacturing : Accounting with Balance Sheet Accounts and Profit and Loss Accounts being selected) no consolidation is happening as if there is no functionality behind this tab.
    Kind regards,
    Sarp

    Hi Sarp,
    You can check the below mentioned link. Unfortunately, this is the only one availbale at the moment..
    Production - Partner Preview - 20131023
    Thanks,
    Joseph

  • Account determintaion with screen shot

    hi ,
         can any one send me account determination with screen shots ..
    email : [email protected]
    rewards for sure
    thanks
    madhan

    Hi,
    I have sent you the mail. It will help you.
    Reward points if solution helps.
    Regards,
    Allabaqsh G. Patil

  • In my account's profile, the entire page is turning into symbols and I cannot download the program as I don't know which one the download button is (have a screen shot if needed)

    I have just purchased Adobe Acrobat XI Standard.  I received all the appropriate emails with serial numbers etc.  I go into my Adobe account so I can download the content and I cannot read the page as all the page content is in symbols.  I obviously don't know what they are saying nor which button it is to download the program.  I have a screen shot of my product's page if necessary.  I have tried going through Internet Explorer and Google Chrome. 

    Hi kirrileeb,
    Are you having trouble with other websites, or just with Adobe? Let's start by clearing the browser cache, and logging back in to http://www.adobe.com. You may also want to try a different web browser as well. Are you able to download Acrobat from this page: Download Acrobat products | Standard, Pro | XI, X?
    If you're still having issues when you're looking at your account on Adobe.com and downloading Acrobat, let us know. If you write back, please let us know what browser you're using, and whether you're on Mac OS or Windows.
    Fingers crossed that all goes well when you clear the cache, but let us know if it doesn't.
    Best,
    Sara

  • Account determination error in Invoice document posting

    Problem - When generating the invoice document to customer, an error is displayed - Document is saved (Account determination error). As a consequence of this step, the invoicing is not able to create FI document
    My Analysis-
    Account determination is done in G/L account assignment (VKOA screen)
    For my billing document, the system is not able to find the GL account (below are screenshots)
    In VKOA screen, I already defined the GL account determination using KOFI procedure.
    I initially defined in table 2 Cust.Grp/Account Key and it didnt work.
    So I defined in both the tables 1 as well - Cust.Grp/MaterialGrp/AcctKey
    But still system is not reading the tables and obtaining the GL account no
    Any advice on why its not working?

    Hi Nikhil,
    As per the screen shots i could observe that you didn't maintained acct asst grp of customer.
    check the acct asst grp of customer field in billing tab is maintained or not.
    other possible reason may be in your pricing procedure -check whether the accounting keys are maintained or not.
    This could solve your issue.

  • Account determination error

    hi
    when i a creating a billing document for third patry sales with refernce to sales order
    while saving the doc i am facing error called account determination error
    can i now where i am wrong
    do i have to amitained ant record in VKOA
    if yes what
    Screen shot
    http://www.4shared.com/file/59857963/f56431d5/fico.html
    Regards
    Vini

    The access you are using for maintaining the condition record. The screen shows the first two accesses which means that there is something wrong with that.
    If your acct determination is not carried out then it will say acct. det has not been done . \
    Looks like your condition records and the acct. determination seems to be a problem.
    GO to acct. det. in BAsic functions- revenue acct detemination I think its VKOA and check your account determnation to see if your account keys and accounts have been correctly maintianed.
    Check your pricing procedure to see if all the relevant condition types have been assigned to the account keys.
    check if your condition records have been maintianed in the correct accesses. It will solce your problem.
    regds
    Jude

  • Cache Cleaner ruined my menu bar, no longer able to screen shot

    not sure if anyone is familiar with this application "Yosemite Cache Cleaner". i just started using it. tried out the light scan and auto restored my computer then messed my top menu bar... well its off screen i can not see the time or the wifi icon it almost looks like the other half of the menu bar is on another screen by HDMI but in this case its not. i have nothing connected to this computer but my midi controller and a pre amp (always) anyways . i have dropbox and g-drive installed i can see those but any notification that pops up i can only see half of it. so of course i contacted this company immediately. i get a response back they are asking me to "screen shot my problem" so i try to screen shot and nothing happens, my screen flashes once and then the more i tried, the more screen flashed with an error sound. can anyone please help me solve this problem?

    First, delete the fake "utility," which is a scam. Caches don't need to be "cleaned."
    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Purchase full cycle process with T-Codes and screen shots

    HI GURUS,
    will anyone mail PO Full Cycle with screen shots? And t-codes
    1. PURCHASING REQUISITION
    2. REQUEST FOR QUOTATION
    3. QUOTATION
    4. PURCHASE ORDER
    5. GOOD'S RECEIPT
    6. INVOICE VERIFICATION
    7. PAYMENT

    The typical procurement cycle for a service or material consists of the following phases:
    1. Determination of Requirements (MD02 / ME51N): - Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
    2. Source Determination: - The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
    3. Vendor Selection and Comparison of Quotations (ME41 / ME47 / ME49): - The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
    4. Purchase Order Processing (ME21N): - The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
    5. Purchase Order Follow-Up: - The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
    6. Goods Receiving and Inventory Management (MIGO): - Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.
    7. Invoice Verification (MIRO): - The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
    Rebate Process:
    1. XK02 - Changing a Vendor Master Record (Activate "Subsequent Settlement" and "Sebseq. sett. index" in Purchasing view)
    2. MEB1 - Creating a Rebate Arrangement
    3. ME21N - Creating a Purchase Order
    4. MIGO - Processing the Goods Receipt for the Purchase Order
    5. MIRO - Processing the Incoming Invoice on the Basis of a Purchase Order
    6. MEB4 - Creating an Interim Settlement
    7. MEU2 - Creating a Business Volume Comparison
    8. MEB2 - Creating a Final Settlement
    A centrally agreed contract is involved if:
    A single purchasing organization procures for an entire corporate group, or
    A reference purchasing organization makes a contract available to other associated purchasing organizations, enabling the latter to issue release orders against this contract
    Centrally Agreed Contracts are created in same transaction ME31K, but here is some difference in maintaining the pricing conditions and partner functions.
    Maintaining Plant Conditions
    1. When maintaining the centrally agreed contract, choose Edit > Plant conditions > Overview.
    2. On the overview screen that then appears, enter the desired plant and choose "Overview" icon Plant prices.
    3. An item overview screen appears, starting from which you can maintain conditions.
    Choose Item > Conditions to access the condition maintenance screen.
    4. Return to the overview and repeat the process for all plants for which you wish to store plant-specific conditions.
    5. Save your input.
    Maintaining Partners
    You can maintain the different partners either in the vendor master record or individually in the contract. If the partners have been maintained in the vendor master, they are suggested in the contract.
    Maintaining partners in a contract
    1. In the contract, choose Header > Partners.
    2. The Data Retention Level: Partners screen appears. Enter the plant and/or vendor sub-range, and choose ENTER. The Maintain Partners screen appears.
    Note
    To see which partners have already been maintained, select the desired item and choose "Display" button Level.
    3. Enter the desired partner and return to the item overview for the contract.
    4. Save your input.
    Maintaining partners in the vendor master
    1. Choose Extras > Different data on the Partner Roles (partner functions) screen in the vendor master record.
    2. On the Create Different Data screen, enter the plant or vendor sub-range and select Partner Roles.
    3. Click "Enter" button. The Change Vendor: Partner Roles screen appears.
    4. Enter the desired partners and click "SAVE" button to save your input.
    Then create Release orders (in ME21N) w.r.t. Centrally Agreed Contrat

  • WorkFlow Tutorials with Screen Shot

    HI Experts,
    Can anyone send WorkFlow Tutorials with Screen Shots??..My email id is <REMOVED BY MODERATOR>.. Full points will be rewarded for this immediate help..Thanks..
    Edited by: Alvaro Tejada Galindo on Jun 6, 2008 1:52 PM

    Hi Satheesh,
    Please find some questions related to WorkFlow
    1. Is there a good book about this subject?
    Yes, "Practical Workflow for SAP" by Rickayzen, Dart, Brennecke and Schneider. Available from SAP press at the end of July. A german translation of this workflow book is also available directly from Galileo-Press, the publisher.
    2. How do I convince my company to use workflow?
    Feedback from user groups emphasizes that although the competitive advantage gained by using workflow eclipses the financial savings, it is the financial savings that are the deciding factor when obtaining support from senior management. Projects getting the blessing at the CEO level are much easier to manage, and far more likely to reach their goal within the project time frame. So plan well, and don't neglect the business case.
    Because the following questions deal with the financial case in more detail, this section will finish by listing the competitive advantages.
    The quality of the process is assured by pushing the relevant information together with links to related transactions directly to the user. Managers don't have the time to search for information so give them what they need to reach the correct decision.
    Cycle time is reduced by pushing the process directly to the users. The users receive notification of a task immediately and can even be prioritized by the system.
    The tasks are performed consistently and diligently by the users. The workflow system pushes all the necessary information needed to perform a task, including a clear description of what has to be done, how to do it and the impact this task has on the business process for your company. At any time, the user can check the list of tasks pending and determine at a glance which are the important tasks, and which tasks can be completed the next day without any negative impact.
    The process instance is transparent. Any user can check at any time how far the process has progressed and which stage the process has reached. For example the call center can immediately see the status of a purchase order, an employee requisitioning a purchase would see at a glance if a colleague has been sitting on it for too long, the ad hoc notes made when approving an engineering change request are visible long after the request has gone into production.
    The process is flexible, allowing it to be changed on the fly without retraining everyone involved. The description accompanying the change takes care of on-the-fly process improvements.
    Deadline handing ensures that users perform the tasks within the time planned. Escalation measures ensure that the failure to meet a deadline can be corrected by other means.
    Intelligent reporting highlights the weaknesses of a process. Often there is a simple cure to such weaknesses such as reeducating the users involved in the bottleneck or providing additional information (automatically). The difficulty of a non-automated process is identifying such bottlenecks.
    The process definition is transparent. You can see at a glance how the process works and who will be selected to perform the different tasks. Think of the workflow as the process book. If you can spot the pattern and define the process without headaches, you can create a workflow definition effortlessly. However, don't forget that if a company has business processes that are erratic and lack a consistent pattern, the company is very likely to be losing a lot of money in terms of lost contracts, labor intensive administration and low customer confidence. It is my personal opinion that automating exactly this type of processes will yield the best returns, but only if you limit yourself to automating the basic skeleton of the process first. Don't get bogged down in the detailed exception handling. That can be done in the next phase once you've checked the process statistics and determined which exceptions are worth tackling.
    As with most software the reasons for automating business processes are primarily to increase the competitive edge of your company and to cut costs. Although the increase in competitively gained by radically reducing process times is by far the most insignificant gain from workflow, you should not ignore the cost savings. The cost saving calculations are needed by upper management in order to approve workflow projects. This upper management signature will be very useful in different phases of the project and cannot be underestimated.
    3. How do I calculate the cost saved by workflow?
    Calculate the cost of the manual process in terms of man hours. Don't neglect the time spent gathering information. Ask the following questions:
    Is the user forced to log into different systems, or scan through printed documentation....?
    Does a skilled user spend time on parts of a task, where less skilled (less expensive) user could do the groundwork? I.e. Can a single task be split into skilled and unskilled tasks to free the skilled worker for work where his/her skills are really needed?
    Is time spent researching the progress of a process (usually done by someone not involved in the process directly)?
    Is time spent determining who to give the task to next?
    Probably the most significant cost will the be the cost of failure?
    How often does the process fail?
    What is the real cost of failure? Loss of a contract? Loss of a customer? Law suit?
    If the failure can be rectified, how labor intensive is it?
    4. What are typical costs saved by workflow?
    A manually processed accounts payable invoice will cost about 25 USD. After workflow enabling about 15 USD (one example based on customer feedback from a user group meeting).
    5. What are typical reductions in processing time caused by workflow?
    A traditional paper based approval process involving three people will typically take seven days to complete. The automated process will take one day (results based on customer feedback).
    6. What do customers say are the strengths of SAP WebFlow?
    WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are:
    Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no gluing....)
    Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business process for your company. Workflows can be up and running including training in under a day (thanks to the knowledgeware delivered as part of the template packet).
    Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, mySAP.com.... Examples of integration are:
    Business Reporting (WIS),
    Context sensitive availability at any time through the system menu (available anytime, anywhere)
    More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown workflows fit the landscape exactly,
    More and more workflow functionality is available directly within the SAP transaction or Web MiniApp.
    WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this.
    7. How are users notified about their work pending?
    The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed.
    The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately.
    This work item can be received and executed in MS OutlookÒ, Lotus NotesÒ, mySAP Workflow MiniApp or the SAP integrated inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly.
    8. What workflow reporting is available and is it useful?
    Standard workflow reports exist which allow the administrator to check statistics such as the frequency and average duration of the workflow processes. However the real strength of the workflow reporting is that it allows reports to be configured which analyze the process statistics in combination with the data involved within the workflow process and the organizational units associated with the process. For example you can determine the average time invested in a failed contract renewal request, the time taken to create material masters in different plants or the frequency of rejected purchase requisitions on a department to department basis. Often, big reducations in cost or cycle time can be obtained without touching the workflow definitions. Reeducating a particular group of users or incorporating supplementary information in a work item description can often cause dramatic improvements on the cycle times of particularly critical subsets of the process. It is not unusual that this may have a big impact on specific products, plants or organizational units. This will show up in the WebFlow reporting in LIS or the Business Warehouse but it might not show up in traditional statistical workflow reporting. Even though the average time does not change significantly, the impact on costs and profit can be dramatic.
    9. How do I choose who to distribute the tasks to?
    A work item is assigned to one or more users. Whoever reserves or executes the task first wins and the work item vanishes from the other users' inboxes. This eliminates the need to assign the user to one single user. I.e. No need for complicated algorithms to determine which single user will receive the work item and no need to worry about what will happen when one user is ill for the week (also taken care of by sophisticated substitution mechanisms which can be linked to the SAP organizational model).
    Tasks can be assigned to an organizational unit but the strength of the workflow system is to enable business rules which select users according to the data being processed. For example, you might have one group of users associated with one quality notification type. The workflow can be configured to query the QM module directly to determine the users. You can define fallbacks using the default role associated with a task and allow agents to be specified on the fly by a supervisor.
    Tasks can be assigned to office distribution lists which is useful when you want your users to subscribe or unsubscribe to a particular task. A typical use of this would be where you have a work rote or want to reduce user maintenance to an absolute minimum. The users subscribe or unsubscribe by joining or leaving an office distribution list (one mouse click).
    10. What happens when a deadline is missed?
    This depends on your workflow definition. In the simplest case an e-mail is sent to another user by the system (typically your supervisor so watch out!). However in more sophisticated scenarios a missed deadline can redirect that path that the workflow takes. One customer uses deadlines to automatically make an approval if the deadline is missed (at about the eighth approval level!!!). This gives the user the chance to make rejections but does not force him/her to go into the system to approve the other 99.9% of the requests. In safety critical environments the workflow might trigger off preventative action when a deadline is missed or might put other processes on hold. There is no limit as to how you can use this functionality.
    11. What deadlines can be monitored?
    Many different types of deadlines can monitored. At the single workflow step level you can define deadlines which trigger when the work item has not completed within a certain time and other deadlines when no one starts working on the work item within a given time. You can specify the task deadline statically (e.g. 1 week) or dynamically (e.g. 1 week for material type A and 2 weeks for all the other materials). The offset can be related to the step (e.g. you have 1 week to complete this step) or related to the process (e.g. complete within 2 weeks of the complete process starting, irrespective of how long your colleagues have hogged the previous steps).
    Last but not least, deadlines can be set for sub-processes, which is often more important than the deadline of a single step in a workflow.
    12. How can I check the status of a workflow?
    This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business object to check the workflow progress. For example, while viewing a purchase order you can select "workflow" from the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached.
    13. How are workflows triggered?
    Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won't boot). Automatically triggered workflows are useful because the operator does not even have to be aware of the workflow's existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement.
    Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we're talking about 50 000 work items a day here!).
    Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed here.
    14. What open interfaces are supported?
    The most significant interface supported is the Wf-XML standard from the Workflow Management Coalition. This is an independent organization of which SAP is a funding member, along with most other major workflow vendors. The Wf-XML interface is based on XML and allows workflows from different vendors to communicate with each other. A detailed description of the interface is available on the WfMCs web site at www.wfmc.org.
    15. What is Wf-XML used for?
    Although a company is far better off workflow enabling their system with SAP WebFlow when SAP software is used anywhere within the process, a collaborative process can take place between partners using different software platforms employing different workflow systems. To support SAP customers in this situation, WebFlow offers the open interface Wf-XML. This allows Business Processes enabled using different tools to communicate and control each other. Any workflow tool offering this interface can connect up with other tools that also offer this interface.
    Wf-XML is the only open interface for supporting interoperability of business processes, independent of what the business process being integrated.
    16. Where does Wf-XML come from?
    Wf-XML comes from the Workflow Management Coalition, an independent body of workflow vendors, customers and higher education establishments.
    17. How does the workflow call procedures from non-SAP systems?
    The Actional control broker integrates directly into SAP WebFlow enabling proxy objects to be called directly from the workflow step. When called, the proxy method will make a call to the outside system either as a background task or as a dialogue step. These proxy objects are generated in the SAP system using a converter which converts the objects interface (DCOM, CORBA...) to the SAP syntax. A syntax converter also lets developers view any object in any of the participating systems in the developer's preferred language.
    18. How can I get the workflow initiator information in my task?
    1) From your triggering event to the workflow, bind the event creator element to the workflow initiator element.
    2) Create a workflow container element based on USR01.
    3) Add a step based on USR01.FINDUSERFROMAGENTSTRUCTURE to convert your initiator to a USR01 object.
    4) Pass the USR01 object to each task you want to display the details.
    Mailing
    19. What differences are there between a work item and a notification mail?
    a) The work item cannot be used to notify several users.
    Mails can be routed to several users, just like work items. When a mail is sent, and one recipient reads and deletes the mail, all other recipients will still have access to their own copy in their own inbox. However, when a work item is processed by one of the recipients it will automatically disappear from all the other inboxes. So you can see that a work item is unsuitable for notifying several users.
    It is also worth noting that a mail can be forwarded in many different ways (fax, internet...) whereas the work item cannot.
    b) The work item holds up the workflow
    When the workflow sends a mail (usually as a background step) it continues with the process immediately after transmitting the mail. When a work item is generated, the workflow will not continue until the work item has been processed. This slows down the process. Occasionally this is what is intended (using the work item as an approval step without the ability to reject) but usually you will better off using mails for notifications.
    Note: You can send business objects as references with the mail either as a business object reference attached to the mail or as an URL (ABAP required).
    What is the difference between sending a mail to a recipient list compared to sending individual mails via a dynamic loop?
    Performance. Sending 1 mail to 20 recipients will cost considerably less performance than sending 20 individual mails. If the mail is sent as a SAP Office mail (as opposed to e-mail, fax...) disk space will also be a factor because the SAP office mail will only exist once in the database, with references being created for each of the recipients.
    The only time you need to consider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another.
    20. How do I send a standard text as an e-mail from workflow?
    It is very easy sending standard text , which may include data from the workflow. You simply create a background step which sends the work item description. This may include variables which will be substituted when mail is sent.
    In early releases you have to create your own task based on the method SELFITEM SendTaskDescription. In later releases a wizard is available for creating the step and in release 4.6 there is even a step type which does this all for you automatically.
    Whichever path you take, there is very good online documentation describing exactly what has to be done.
    21. How do I send a complex text from the workflow?
    You may create mails using SAPscript. These mails can include conditions which are evaluated in order to determine which text blocks which are used in the mail. Workflow variables can be used in these conditions and workflow variables can be substituted into the body of the e-mail text.
    22. How do I send really complex mails from the workflow?
    If you this is not enough for you will probably want to write your own ABAP routines for generating the text and generating the attachments to go with the text.
    Use the function group SO01 which contains functions of the form SO_*_API1 which are ideal for creating your own sophisticated messages. There are plenty of advantages of how these are used within the SAP system.
    23. How do I send reports?
    There are wizards (Release 3.1) which will create workflows for you to send reports to a distribution list. You can specify whether the results should be transmitted or evaluated at the time the recipient wishes to view the report. It is usually better to send the evaluation because this allows the recipient to see the results instantaneously, without having to wait for the report to execute first.
    Deadlines
    24. How can I configure the workflow so that different types of messages are sent out to different people depending on how late the processing is?
    Follow these steps:
    1. Specify a deadline period for the step.
    2. Specify a name for the event. This adds new branch from the step.
    3. Add a new step to the branch which sends a mail message.
    4. Add another step to the branch which sends out the second deadline warning (see mail steps above). Use deadlines in this step to configure an earliest start so that the second message is not sent until a further time has elapsed.
    5. Repeat step 5 as often as you like.
    25. How can I configure the workflow so that when the deadline is missed the workflow step is simply skipped?
    This is tricky to explain but easy to implement once you know how.
    Follow these steps (in later releases there is a wizard which takes you through the steps):
    1. In the terminating events view of the workflow step activate the "obsolete" event and give it a name.
    2. Specify a deadline period for the step.
    3. Specify a name for the event. This adds new branch from the step.
    4. Add a new step to the deadline path. This step must be of type "process control".
    5. Select the control "Make step obsolete" and use the search help to specify the workflow step that has the deadline. Only steps with obsolete paths defined will be displayed (see step 1).
    26. How do I trigger a workflow with an e-mail?
    You can customize the system to call a BOR method when an external mail (fax, e-mail...) arrives in the system. You BOR method should either trigger the e-mail directly or trigger an event. To customize this user exit use the transaction SCOT.
    27. How can I make sure that user's access their tasks via the workflow and not via the menu or launch pad?
    The routing mechanism for work items uses roles and organizational assignments to determine who receives which work item. However the routing does not provide extra authorization checks based on the routing configuration. If you want to ensure that the tasks are executed within the workflow, and not via the standard transaction, service or MiniApp, then you will have to apply your own protection.
    The simplest way of doing this is to remove the standard transaction from the user's menu or Workplace role (but include it in the supervisor's role, just in case).
    If you want to allow the user to execute the task from the menu if and only if they have received the work item then you should replace the standard transaction with your own custom built transaction. Your own transaction simply calls the standard transaction but performs it's own authorization check first, based on the routing mechanism used in the workflow. Tip: Add a second (ored) authorization check to make sure that a supervisor can execute the transaction in an emergency.
    28. What is a workflow? What is a single-step task?
    A single-step task is based on an object type from the object business repository (BOR) (for example, a purchase order) and a method for the object (for example, change). A workflow can contain several single-step tasks and activities such as loops and forks. Through a workflow, you create a logical sequence for the single-step tasks. The tool for creating or changing these types of workflows (workflow template) is the Workflow Builder (transaction SWDD).
    29. What is a work item (important terms)?
    A work item is the runtime object of a workflow or of a single-step task.You can execute dialog work items with the inbox (transaction SBWP). Each workflow and single-step task started is assigned a unique number known as the work item ID.
    30. How is an event triggered from the application and a workflow then started?
    An event can be triggered from the application in three different ways:
    Directly:
    Within the application, the SWE_EVENT_CREATE function module or the SWE_EVENT_CREAT_IN_UPD_TASK function module, for example, generates an event in the update.
    With a change document:
    Change documents are written within the application when you change application objects in the update. You can link events that have the same key with these types of change documents via transaction SWEC.
    With status management:
    The SWE_EVENT_CREATE_STATUS function module triggers an event in the same way as the direct method when a status is changed. This event contains the object type (for example, purchase order), the object key (for example, purchase order 4711) and other information. Using transaction PFTC, you can assign the event to a specific workflow or single-step task. More settings are available in transaction SWE2.
    31. How are the responsible agents determined?
    You can assign agents to a single-step task in transaction PFTC. For example, you can do this using organizational units, work center roles or positions. Within a workflow pattern, you can assign specific agents for this workflow to a single-step task. The overlap between both numbers of 'possible agents' represents the number of agents ('selected agents') who have the work item in the inbox later.
    32. What is the difference of between an e-mail and a work item?
    E-mails and work items are two completely separate things. They just happen to be displayed in the same inbox. An e-mail is a message sent to one or several people. However, a work item is a runtime object of a single-step task or workflow. Consequently, a work item cannot be deleted from the inbox of a user. In this case in fact, you have to adjust the agent assignment or delete the work item as described in note 49545.
    33. PFAC no longer works for my role responsibility setup...
    Use tx: OOCU_RESP
    34. How do I transport workflow definitions and agent assignments?
    When transporting workflows, you have to differentiate between the workflow definition and the agent assignment.
    A workflow definition is a workbench request. When you save the workflow, a workflow version is created and a request written. Further information about the transport or about the status management is provided in note 378487 and in the notes mentioned there under related notes.
    However, where the agent assignment is concerned, this is a Customizing request. To allow transport of agent assignments, the value of the semantic abbreviation CORR for the TRSP group name must be empty in table T77S0.
    35. How do you debug a background workflow process?
    In your method write the following code:
    data exit.
    Do.
    if exit = 'X'.
    exit.
    endif.
    enddo.
    Run the workflow, causing an infinite loop on that step, and then go to SM50.
    Here you can debug the process.
    36.What is the Workflow basic Customizing?
    Before you can use the Workflow module, you must first execute the basic Customizing in transaction SWU3. All of the listed points should be green (the number range for customer tasks is no longer required). A detailed description of the activities is provided in the relevant information buttons. You can also execute some (but not all) of the points using the Automatic Customizing button. See the online documentation for an exact description of what happens there. The RFC destination must work correctly and the user (usually WF BATCH) should have the SAP_ALL profile.
    37.: What options do I have as a user to configure the inbox individually?
    You have the following options:
    You can create separate user-dependent or user-independent layouts so that you can adapt the displayed columns individually. You can access the function in the Workplace via an application function key.
    You can set filters to set certain criteria for individual columns or several columns simultaneously, according to which specific work items are then filtered.
    You can add dynamic columns in the layout that then display dynamic elements for certain tasks and users from the work item container. However, this is only possible if all tasks in the inbox belong to just one task. If they have several tasks in the inbox, filtering serves no useful purpose because all tasks are first completely read once. You can define these dynamic columns using transaction SWL1.
    38. What does the substitute rule system look like in the workflow?
    You have a choice of two different substitute rulings:
    Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).
    Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.
    For other questions, you must also refer to note 74000.
    39. How can users be automatically notified that new work items are available for processing?
    Unfortunately, the dialog box that informs users of new work items which appears in SAPoffice is not available within SAP Systems.
    However, the following two options are provided:
    In the Workflow Builder, you can designate the item as an express item via additional data. The user then receives a corresponding express dialog box.
    The RSWUWFML report (note 131795) is a more flexible option. This report sends an e-mail to an external Internet address to notify the user of new work items.
    40. Can I set deadlines for the latest processing of work items?
    this is where you can use deadline monitoring for work items. In the Workflow Builder, you can set dates for a requested/latest start/end date for each individual step. You must schedule the SWWDHEX job via transaction SWU3 for this. Schedule the job permanently in the production system otherwise it is difficult for the job to schedule individual deadline monitoring scenarios when workflow is heavy.
    41. Can I also execute work items with external programs such as Outlook?
    You can use the Web GUI for HTML instead of the Windows GUI. However, note that some functions do no work in the WEB GUI, due to technical restrictions in the browser. You must refer to note 487649 on this subject.
    SAP also provides interfaces which allow you to process work items with external programs such as Lotus Notes or Microsoft Outlook. Refer to notes 77099, 98408 and 454845 for details.
    More stuff on WORKFLOW
    Transactions
    AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard
    MCA1 Workflow Information System Reporting -> Workflow Information System (WIS)
    OOAW Evaluation paths
    PFAC Maintain standard roles
    PFAC_CHG Change roles Definition tools -> Standard roles -> Change
    PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete
    PFAC_DIS Display roles Definition tools -> Standard roles -> Display
    PFAC_INS Create roles Definition tools -> Standard roles -> Create
    PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments
    PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments
    PFSO Organizational environment of a user
    PFT Maintain customer task
    PFTC General task maintenance
    PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change
    PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy
    PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete
    PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display
    PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create
    PFTR Standard task for transaction
    PFTS Standard task
    PFWF Maintain workflow task (customer)
    PFWS Maintain workflow template
    PPOC Create organizational plan Definition tools -> Organizational plan -> Create
    PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change
    PPOS Display organizational plan Definition tools -> Organizational plan -> Display
    SWDA Ongoing Settings Administration -> Settings
    SWDC Workflow editor administration data
    SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer
    SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages
    SWE3 Display instance linkages Utilities -> Events -> Instance linkages
    SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off
    SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage
    SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties
    SWEL Display event log Utilities -> Events -> Event log -> Display
    SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer
    SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository
    SWI1 Selection report for workflows Utilities -> Work item selection
    SWI2 Work item analysis Reporting -> Work item analysis
    SWI3 Workflow outbox Runtime tools -> Workflow outbox
    SWI4 Task analysis Reporting -> Task analysis
    SWI5 Workload analysis Reporting -> Workload analysis
    SWI6 Object links Runtime tools -> Object links
    SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox
    SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF)
    SWL1 Settings for dynamic columns Customizing, part of ongoing settings
    SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment
    SWLD Workbench for Workflow 4.0
    SWLP Copy plan version
    SWLV Maintain work item views Customizing, part of ongoing settingS
    SWLW Workbench for Workflow 3.0
    SW01 Business Object Builder Definition tools -> Business Object Builder
    SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide
    SWU0 Event simulation Utilities -> Events -> Simulate event
    SWU2 RFC monitor Utilities -> Workflow RFC monitor
    SWU3 Customizing consistency check Utilities -> Customizing
    SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task
    SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task
    SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task
    SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template
    SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off
    SWU9 Display technical trace Utilities -> Technical trace -> Display
    SWUD Diagnostic tools Utilities -> Diagnosis
    SWUE Trigger event Utilities -> Events -> Generate event
    SWUF Runtime system administration Administration -> Runtime system
    SWUG Workflow start transactions Definition tools -> Workflow start transactions
    SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow
    SWUS Start tasks Runtime tools -> Start workflow
    SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message"
    SWX1 Create notification of absence
    SWX2 Change notification of absence
    SWX3 Display notification of absence
    SWX4 Approve notification of absence
    SWXF Form applications: Access point Environment -> Demo examples -> Fill out form
    Reports
    RSWWWIDE – Delete work items
    RHSOBJCH to fix PD Control Tables
    Tables
    SWW_OUTBOX - Lists Workflows in outbox together with status
    SWW_CONT - Container Contents for Work Item Data Container
    SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects)
    SWWLOGHIST- History of a work item
    SWWORGTASK- Assignment of WIs to Org.Units and Tasks
    SWWUSERWI - Current Work Items Assigned to a User
    SWWWIHEAD - Header Table for all Work Item Types
    <REMOVED BY MODERATOR>
    Regards,
    Amber S
    Edited by: Alvaro Tejada Galindo on Jun 6, 2008 1:51 PM

  • Rebate screen Shots

    Hi SAP Gurus,
    Plz has anybody for me rebate screen shots also? my mail iD : [email protected]

    Dear Ngassom Yves Fabrice,
    How to do rebate processing
    Rebates Processs in SAP is divided into three components
    1) Configuring Rebates
    2) Setting Up Rebates
    3) Managing rebate agreeeements and payments
    Pre-requsiistes- Check the following:
    1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab.
    2.The Billing type must be marked as relevant for rebates.
    3.The Sales Organisation must be marked as relevant for rebates.
    Condition Technique :
    Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..
    Use create access sequence (AS).  Enter 1 in field category for rebate specific.  AS after going thru the right path of maintaining access sequence for rebates.
    The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time.
    Rebate related condition types are identified by codnition class -C.
    After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.
    The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.
    Now payment of rebates:
    Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn.  You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period.
    These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created
       Customer account/ is debited and
       Accrual provision account is credited.
    Also, please note that when rebates are created without dependent ona material but on customer/material you need to refer to a material for settlement.
    With Compliment: Srini
    I have this same problem found in:
    http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htm
    However, can somebody explain it as I have problem in understanding the link.
    What exactly do you wish to know in Rebates? The total outline of the Rebate process or each and every step in the SAP system?
    First of all rebates are more or less discounts which are offered to customers. The rebates are based on the volume of the business the customer does with you within a specified time. for eg if the customer agrees for Rs.1 Crore worth of business with u in 1 year, then you activate your rebate porocess. if at the end of the year the customer DOES achieve the target u offer him say 2/3/4 % whatever is decided. The rebates are passed on to the customer in the form of Credit notes.
    The rebate can be given to the customer at one time or in installments also.
    This is broadly the outline of the rebate process.
    R.Sreeram
    Note : I recomend you to study the theory part of why rebate and why not a discount.
    This will help you understand better.
    May be I can help you with rebate process.(IN -IMG)
    1. define a rebate agreement type
    2. define a condition type group
    3. define a condition type and place this condition
    Type in the pricing procedure.(REQUIREMENT=24)
    ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU
    YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.
    Once you have defined all the 3 and assignment starts.
    Assign the agreement type to the condition type group
    Assign the cond type group to the condition type.
    Condition technique is also used in rebates.
    REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR THE BILLING DOCUMENT.
    After having done this please proceed to maintain the condition record for the rebates (transaction code-vbo1)
    Note: if you maintain the requirement coloumn with the requirement as 24 - the rebate will be affected in the billing document and if you dont give the requirement as 24 your rebate will be affected in the sales order.
    The rebate process is completed when you have created a credit memo to the customer.
    The document type for the partial settlement is R3.
    Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first you try with the standard condition type boo1, boo2
    boo3 boo4.
    AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER , DELIVERY AND BILLING.
    GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE ACCOUNT PARTIALLY.
    I hope this will be of any help to you.
    In a simple way,
    1. First you need to create a Rebate agreement.
    2. Create condition record for rebate giving the rebate rate and accrual rate.
    3. when the rebate relevent billing doc is generated, the rebate and accruals are determined and posted in a seperate GL account as a noted item - amount to be settled. Also it gets copied in the rebate agreement.
    4. create settlement run using credit memo request and then credit memo to settle this amount with the customer.
    Hope this helps you.
    Do award points if you found them useful.
    Regards,
    Rakesh
    P.S. you can send me a mail at my mail id [email protected] for any specific details

  • Plz requesting kindly for screen shots of intercompany and third party sale

    Hi btothers,
    Am into new project where we have intercompany sales and third party sales ,can any one plz send me with step by step screen shots to my mail id [email protected]
    Thanks & regards,
    srinivas

    Hi Srinu,
    Please find below the complete Documentation on Third Party Sales and Intercompany Process.
    THIRD PARTY SCENARIO:
    In third-party order processing, your company does not deliver the items requested by a customer. Instead, you pass the order along to a third-party vendor who then ships the goods directly to the customer and bills you. A sales order may consist partly or wholly of third-party items. Occasionally, you may need to let a vendor deliver items you would normally deliver yourself.
    Process Flow
    The processing of third-party orders is controlled via material types. Material types define whether a material is produced only internally, can be ordered only from third-party vendors, or whether both are possible. For example, a material that is defined as a trading good can only be ordered from a third-party vendor. However, if you manufacture your own finished products, you may also want, from time to time, to be able to order the same type of product from other vendors.
    Processing Third-Party Orders in Sales
    Third-party items can be created automatically by the system, depending on how your system is set. However, you can also change a standard item to a third-party item during sales processing manually.
    Automatic third-party order processing
    If a material is always delivered from one or more third-party vendors, you can specify in the material master that the material is a third-party item. During subsequent sales order processing, the system automatically determines the appropriate item category for a third-party item: TAS. To specify a material as a third-party item, enter BANS in the Item category group field in the Sales 2 screen of the material master record.
    Manual third-party order processing
    In the case of a material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing. For a material that you normally deliver yourself, you specify the item category group NORM in the material master.
    If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
    If address data for the ship-to party is changed in the sales order in third-party business transactions, the changed data will automatically be passed on to purchase requisition and also to the purchase order ,if one already exists. In the purchase order, you can display the address data for the ship-to party in the attributes for the item.
    You can only change the address data for the ship-to party in the sales order for third-party business transactions, and not in the purchase order.
    Processing Third-Party Orders in Purchasing
    When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
    Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
    All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order
    You process third-party items by creating a normal sales order. In overview for the order, you can then overwrite the default item category (TAN in the standard system) with the special item category for third-party items: TAS
    Billing Third-Party Orders
    If relevance for billing indicator for the item category has been set to B (relevant for order-related billing on the basis of the order quantity) in Customizing, the system includes the order in the billing due list immediately. If, however, the indicator has been set to F (relevant to order-related billing on the basis of the invoice quantity), the system does not include the order in the billing due list until an invoice from the vendor has been received and processed by the purchasing department. In the standard system, item category TAS (third-party order processing) has been given billing-relevance indicator F.
    In the first case, the third-party order is considered to be completely billed only when the invoiced quantity equals the order quantity of the sales order item. In the second case, each time a vendor invoice is received, a customer invoice is created for the quantity in the vendor invoice and the order is considered to be fully invoiced until the next vendor invoice is received.
    If you have activated billing-relevance indicator F for item categories in Customizing, billing can refer to the goods receipt quantity instead of the incoming invoice quantity.
    You can control whether the invoice receipt quantity or the quantity of goods received is relevant for billing in Customizing for copying control for billing at item level.
    FOR YOUR PROCESS Individual Purchase Orders WELL GIVE THE RIGHT SOLUTION
    Individual purchase orders are used when your customer orders goods from you that are not in stock and must be ordered from one or more external vendors.
    Process Flow
    During sales order entry, the system automatically creates a purchase requisition item. The purchasing department creates a purchase order based on the requisition and the vendor ships the goods directly to you (unlike third party order processing, where the vendor ships directly to your customer). You then ship the goods to your customer. While the goods are part of your inventory, you manage them as part of the sales order stock. Sales order stock consists of stock that is assigned to specific sales orders and cannot be used for other purposes.
    Process Flow for 3rd Party Sales
    Customize the third party sales in summary:
    Prerequisites for 3rd party sales,
    Purchasing org,
    purchasing group,
    assign the Purchase org to company code
    assign Purchase org to plant,
    should not maintain the stock in material, it should be trading goods,
    1. Create Vendor XK01
    2. Create Material – Material Type as "Trading Goods". Item category group as "BANS".
    3. Assign Item Category TAS to Order type that you are going to use.
    4. A sale order is created and when saved a PR is generated at the background
    5. With reference to SO a PO is created (ME21N). The company raises PO to the vendor.
    6. Vendor delivers the goods and raises bill to company. MM receives the invoice MIRO
    7. Goods receipt MIGO
    8. Goods issue
    9. The item cat TAS or Schedule line cat CS is not relevant for delivery which is evident from the config and, therefore, there is no delivery process attached in the whole process of Third party sales.
    10. Billing *--
    SD - 3rd party sales order Create Sales Order
    VA01
    Order Type
    Sales org, distr chnl, div
    Enter
    Sold to
    PO #
    Material
    Quantity
    Enter
    Save
    SD - 3rd party sales order View the PR that is created with a third party sales order
    VA01
    Order Number
    Goto Item Overview
    Item ->Schedule Item
    SD - 3rd party sales order View the PR that is created
    ME52N
    Key in the PR number
    Save
    SD - 3rd party sales order Assign the PR to the vendor and create PO
    ME57
    Key in the PR number
    Toggle the "Assigned Purchase Requisition"
    Execute
    Check the box next to the material
    Assign Automatically button
    Click on "Assignments" button
    Click on "Process assignment"
    The "Process Assignment Create PO" box , enter
    Drag the PR and drop in the shopping basket
    Save
    SD - 3rd party sales order Receive Goods
    MIGO_GR
    PO Number
    DN Number
    Batch tab , click on classification
    Serial Numbers tab
    Date of Production
    Flag Item OK
    Check, just in case
    Post
    Save
    SD - 3rd party sales order Create Invoice
    MIRO
    Invoice Date
    Look for the PO , state the vendor and the Material
    Check the box
    Click on "Copy"
    Purchase Order Number (bottom half of the screen)
    Amount
    State the baseline date
    Simulate & Post
    Invoice Number
    *Invoice blocked due to date variance
    SD - 3rd party sales order Create a delivery order
    VL01N
    In the order screen , go to the menu Sales Document , select "Deliver"
    Go to "picking" tab
    State the qty and save
    SD - 3rd party sales order Create a billing document
    VF01
    Ensure that the delivery document is correct in the
    Enter
    Go to edit -> Log
    Save
    Third party order processing is as follows:
    Assume three companies X, Y and Z
    X - The company,
    y - The customer
    Z - Vendor
    When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
    If he is procuring the goods, there are two methods that are generally followed:
    Method 1) After receiving the PO from Y, X creates a sales order against Y.
    Now at the same time he also creates a PO to a vendor Z to produce the goods
    Z produces the goods and supplies to X
    X receives the goods from Z
    Then X delivers the same goods to Y.
    After that X invoices Y and Z invoices X.
    Note : Here there is no direct/ Indirect relation between Z and Y.
    This process is known as Trading Process. and the Material here is created with Material type HAWA.
    The other method is a Third party order processing method:
    Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
    X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
    Now Z supplies the material to Y and acknowledges the same to X.
    Z will send a copy of delivery acknowledgement and invoice to X.
    After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
    The next step for X is to create an invoice and submit to Y
    Only after the invoice verification document is posted then only X can create an invoice for Y.
    This is the business flow that is followed for third party order configuration.
    There are few steps that have to be configured to enable the system to function as mentioned above.
    Step1)
    If you are always following a third party process for a material then you have to create the material using item category group BANS.
    The procurement type should be marked as External procurement (F) in MRP 2 view of the material master record.
    if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurement ( in house manufacturing and external procurement).
    Step 2)
    the item category in the order should be manually changed as TAS.
    For that you need to configure the item category determination
    Order type + item cat Group + Usage + High level = Item cat + Manual item cat
    OR + NORM + + = TAN + TAS
    OR + BANS + + = TAS
    Step 3)
    make sure that during the item category configuration for TAS you need to mark relevant for billing indicator as F
    step 4)
    The schedule line category for this type should be CS.
    make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requisition order immediately after the creation of the sales order and the PO to vendor is created against this purchase requisition.
    Intercompany Process:
    Go through the explanation given below with test cases.
    Business case: -
    Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.
    SPRO Customization required:-
    1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)
    2. Maintain intercom any billing type as IV for sales document type OR
    3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)
    4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)
    5. Automatic posting to vendor account (Optional)
    6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing
    Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing
    Master data to be maintained:-
    1. Create end customer master in company code/sales org 4211/RT/11
    2. Create customer master for 4211 company code/sales org in 4436/RT/11
    3. Maintain PR00 as price for end customer-Active in RVAA01
    4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01
    5. Maintain IV01 as inter-company Price-Active in ICAA01
    Process:-
    1. Create OR with sold to party as end customer.
    2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.
    3. Pricing procedure is RVAA01
    4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
    5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
    6. Delivering sales org will create intercompany billing IV with reference to delivery document.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Screen shots for time mgmt

    Hi  every one
    I am not good in Time Mgmt. mainly I want screen shots for Holiday Calendar, Break Schedule, DWS,PWS, WSR, Variants, Day types and Planed working time. So I am looking for a screen shots. Could you please help me? I would like to practice it over the system by using the screen shots which is already prepared by some body
    Can anybody help me. It is very useful for me.
    Thanks and regards
    Seenu

    why do u want screen shots
    The following is the config. document of TM.
    I think its helpful to u.
     Work Schedules  Personnel Time Management IMG Define Public Holiday Classes
    Work Personnel Time Management IMG Group Personnel Subareas for the
    Work Personnel Subarea Groupings Schedules Schedule
    Personnel Work Schedules  Personnel Time Management IMG Group
    Personnel Subareas for theDaily Work ScheduleSubarea Groupings
     Daily Work Schedules  Work Schedules  Personnel Time Management
    IMG Define Daily Work Schedules
    Work Personnel Time Management IMG Define Period Work Schedules.
    Period Work Schedules Schedules
    IMG Define Day Day Types  Work Schedules Personnel Time Management Types.
     Day Types  Work Schedules  Personnel Time Management IMG Define Day Types.
    Day Work Schedules  Personnel Time Management IMG Define Special Days.Types
    Work Personnel Time Management IMG Define Employee Subgroup Work
    Schedule Rules and Work Schedules Schedules Groupings
    Work Work Schedules  Personnel Time Management IMG Define Groupings
    for the Public HolidaySchedule Rules and Work Schedules Calendar.
    Work Work Schedules  Personnel Time Management IMG Set Work
    Schedule Rules and WorkSchedule Rules and Work Schedules Schedules.
    Work Work Schedules  Personnel Time Management IMG Generate Work
    Schedules ManuallySchedule Rules and Work Schedules
    IMG Set Planned Working Time  Work Schedules  Personnel Time
    Management  Default Value for the Work Schedule.
     Personnel Time Management IMG Set Default Value for Time
    Management Planned Working Time Work Schedules Status.
    Time Data Recording and Personnel Time Management IMG Define
    Personnel Subareas for Substitution Substitutions Administration
    Types.
    Time Data Recording and Personnel Time Management IMG Set Defaults
    for Substitution Types. Substitutions Administration
    IMG Absences Time Data Recording and Administration  Personnel Time
    Management  Group Personnel Subareas for Attendances and Absence
    Catalog  Absences.
    Time Data Recording and Personnel Time Management IMG Define Absence
    Types. Absence Catalog  Absences Administration
    IMG  Absences  Time Data Recording and Administration Personnel
    Time Management Define Counting Classes for the Period Work Absence
    Counting Absence Catalog Schedule.
    Time Data Recording and Personnel Time Management IMG Rules for
    Absence Counting  Absence Catalog  Absences Administration Group
    Employee Subgroups for Time Quotas.Absence Counting (New)
    IMG  Absences  Time Data Recording and Administration Personnel
    Time Management Group Rules for Absence Counting (New)  Absence
    Counting Absence Catalog Personnel Subareas for Time Quotas
    Time Personnel Time Management IMG Absence Absence Catalog 
    Absences Data Recording and Administration Define Rules for Rounding
    Counted Rules for Absence Counting (New) Counting Absences
    Time Data Recording and Personnel Time Management IMG Rules for
    Absence Counting  Absence Catalog  Absences Administration Define
    Counting RulesAbsence Counting (New)
    Personnel TimeIMG Absence Catalog Absences  Time Data Recording and
    Administration Management  Define Counting Rules  Rules for Absence
    Counting (New)  Absence Counting  Deduction rules for Absence quotas
    Time Personnel Time Management IMG Absence Absence Catalog 
    Absences Data Recording and Administration Assign Counting Rules to
    Absence Types.Counting
    Personnel TimeIMG Attendances/Actual Working Time Data Recording and
    Administration Management Define Attendance Types.Times
    Time Personnel Time Management IMG  Attendances/Actual Working
    Times Data Recording and Administration Assign Counting Rules for
    Attendance counting (New) Attendance counting Rules to Attendance
    Types.
    Time Data Personnel Time Management IMG Managing Time Accounts Using
    Attendance/AbsenceRecording and Administration Define Absence Quota
    Types. Time Quota Types Quotas
    PersonnelIMG Managing Time Time Data Recording and Administration
    Time Management  Calculating Absence Entitlements Accounts Using
    Attendance/Absence Quotas Permit Quota Generation Without
    TimeAutomatic Accrual of Absence Quotas Evaluation.
    Time Time Evaluation  Personnel Time Management IMG Set Personnel
    Subarea Groupings for Time Recording.Evaluation Settings
    PersIMG  Time Data Recording and Administration onnel Time
    Management Calculating AbsenceManaging Time Accounts Using
    Attendance/Absence Quotas  Set Base Entitlements  Rules for
    Generating Absence Quotas Entitlements Base Entitlement for Absence
    Quota Generation.
    Personnel TimeIMG Managing Time Accounts Time Data Recording and
    Administration Management Rules for Calculating Absence Entitlements
    Using Attendance/Absence Quotas Determine Validity and Deduction
    Periods.Generating Absence Quotas
    IMG Managing Time Data Recording and Administration  Personnel Time
    Management  Calculating Absence EntitlementsTime Accounts Using
    Attendance/Absence Quotas Define Set Base Entitlements  Rules for
    Generating Absence Quotas  Generation Rules for Quota Selection.
    Define Public Holiday Work Schedules  Personnel Time Management IMG Classes
    Personnel Work Schedules  Personnel Time Management IMG Group
    Personnel Subareas for the Work ScheduleSubarea Groupings
    IMG Group Personnel Subarea Groupings  Work Schedules Personnel
    Time Management Personnel Subareas for theDaily Work Schedule
     Daily Work Schedules  Work Schedules  Personnel Time Management
    IMG Define Daily Work Schedules
    Work Personnel Time Management IMG Define Period Work Schedules.
    Period Work Schedules Schedules
    IMG Define Day Day Types  Work Schedules Personnel Time Management Types.
     Day Types  Work Schedules  Personnel Time Management IMG Define Day Types.
    Day Work Schedules  Personnel Time Management IMG Define Special Days.Types
    Work Personnel Time Management IMG Define Employee Subgroup Work
    Schedule Rules and Work Schedules Schedules Groupings
    Work Work Schedules  Personnel Time Management IMG Define Groupings
    for the Public HolidaySchedule Rules and Work Schedules Calendar.
    Work Work Schedules  Personnel Time Management IMG Set Work
    Schedule Rules and WorkSchedule Rules and Work Schedules Schedules.
    Work Work Schedules  Personnel Time Management IMG Generate Work
    Schedules ManuallySchedule Rules and Work Schedules
    IMG Set Planned Working Time  Work Schedules  Personnel Time
    Management  Default Value for the Work Schedule.
     Personnel Time Management IMG Set Default Value for Time
    Management Planned Working Time Work Schedules Status.
    Time Data Recording and Personnel Time Management IMG Define
    Personnel Subareas for Substitution Substitutions Administration
    Types.
    Time Data Recording and Personnel Time Management IMG Set Defaults
    for Substitution Types. Substitutions Administration
    IMG Absences Time Data Recording and Administration  Personnel Time
    Management  Group Personnel Subareas for Attendances and Absence
    Catalog  Absences.
    Time Data Recording and Personnel Time Management IMG Define Absence
    Types. Absence Catalog  Absences Administration
    IMG  Absences  Time Data Recording and Administration Personnel
    Time Management Define Counting Classes for the Period Work Absence
    Counting Absence Catalog Schedule.
    Time Data Recording and Personnel Time Management IMG Rules for
    Absence Counting  Absence Catalog  Absences Administration Group
    Employee Subgroups for Time Quotas.Absence Counting (New)
    IMG  Absences  Time Data Recording and Administration Personnel
    Time Management Group Rules for Absence Counting (New)  Absence
    Counting Absence Catalog Personnel Subareas for Time Quotas
    Time Personnel Time Management IMG Absence Absence Catalog 
    Absences Data Recording and Administration Define Rules for Rounding
    Counted Rules for Absence Counting (New) Counting Absences
    Time Data Recording and Personnel Time Management IMG Rules for
    Absence Counting  Absence Catalog  Absences Administration Define
    Counting RulesAbsence Counting (New)
    Personnel TimeIMG Absence Catalog Absences  Time Data Recording and
    Administration Management  Define Counting Rules  Rules for Absence
    Counting (New)  Absence Counting  Deduction rules for Absence quotas
    Time Personnel Time Management IMG Absence Absence Catalog 
    Absences Data Recording and Administration Assign Counting Rules to
    Absence Types.Counting
    Personnel TimeIMG Attendances/Actual Working Time Data Recording and
    Administration Management Define Attendance Types.Times
    Time Personnel Time Management IMG  Attendances/Actual Working
    Times Data Recording and Administration Assign Counting Rules for
    Attendance counting (New) Attendance counting Rules to Attendance
    Types.
    Time Data Personnel Time Management IMG Managing Time Accounts Using
    Attendance/AbsenceRecording and Administration Define Absence Quota
    Types. Time Quota Types Quotas
    PersonnelIMG Managing Time Time Data Recording and Administration
    Time Management  Calculating Absence Entitlements Accounts Using
    Attendance/Absence Quotas Permit Quota Generation Without
    TimeAutomatic Accrual of Absence Quotas Evaluation.
    Time Time Evaluation  Personnel Time Management IMG Set Personnel
    Subarea Groupings for Time Recording.Evaluation Settings
     Time Data Recording and Administration  Personnel Time Management
    IMG Managing Calculating AbsenceTime Accounts Using
    Attendance/Absence Quotas  Set Base Entitlements  Rules for
    Generating Absence Quotas Entitlements Base Entitlement for Absence
    Quota Generation.
    Personnel TimeIMG Managing Time Accounts Time Data Recording and
    Administration Management Rules for Calculating Absence Entitlements
    Using Attendance/Absence Quotas Determine Validity and Deduction
    Periods.Generating Absence Quotas
    IMG Managing Time Data Recording and Administration  Personnel Time
    Management  Calculating Absence EntitlementsTime Accounts Using
    Attendance/Absence Quotas Define Set Base Entitlements  Rules for
    Generating Absence Quotas  Generation Rules for Quota Selection.
    Still have doubts defnately i willl do the need ful

  • Who can explain the account determination in SD...

    Hi,
    For example:
    1)How account setting involved in SD?
    2)Why we need set account in SD?
    3)Normally used account config in SD process???
    4)How FI and SD intergrated for those terms like sales revenue, cash discount, sales discount, sales return..??
    5)Would be very better if anyone could attach an detail document on FI-SD with SAP screenshot steps....
    I am really confused with FI terms...
    Thank you very much!!!

    Dear Hoo Laa
    1)How account setting involved in SD?
    It is based on G/L Accounts.  For each G/L account, the chart of accounts contains the account number, account name, and the information that controls how an account functions and how a G/L account is created in a company code.
    Charts of accounts can have three different functions in the system:
    - Operating chart of accounts
    The operating chart of accounts contains the G/L accounts that you use for posting in your company code during daily activities. Financial Accounting and Controlling both use this chart of accounts.
    You have to assign an operating chart of accounts to a company code.
    - Group chart of accounts
    The group chart of accounts contains the G/L accounts that are used by the entire corporate group. This allows the company to provide reports for the entire corporate group.
    The assigning of an corporate group chart of accounts to a company code is optional.
    - Country-specific chart of accounts
    The country-specific chart of accounts contains the G/L accounts needed to meet the country's legal requirements. This allows you to provide statements for the country's legal requirements.
    The assigning of an country-specific chart of accounts to a company code is optional.
    2)Why we need set account in SD?
    Bcoz only marketing people will only decide how to post in FI that particular invoice.  That is whether it is normal sales, sample sales, scrap sales etc.,  Depending upon that they (SD) people will maintain respective document types and pricing procedure.  In almost all companies, since invoice would be generated by marketing people, in pricing procedure, we need to define which condition types should pass on to FI; which should not
    3)  Sorry not able to understand exactly your question
    4)  How FI and SD intergrated for those terms like sales revenue, cash discount, sales discount, sales return..??
    It is based on the Account Keys and Tax Codes which FI people will maintain and SD will assign these Account Keys in their Pricing Procedure.  Based on this, determination of Accounts will happen
    5) Would be very better if anyone could attach an detail document on FI-SD with SAP screenshot steps....
    Sorry not possible to attach screen shots in this forum.
    thanks
    G. Lakshmipathi

  • Interest account determination

    hi guys
                i have one doubt in interest configuration on account determination. we have configure for customers and vendors. i have four t codes for it.
    1)obv1- Interest on A/R arrears
    2) obv9 --Interest on A/P arrears
    3) obv4 --Vendor interest scale
    4) obv3 --Customer interest scale
                these all are related 2 account determination for vendors and customers rite. so can any one tell me what are the accounting entries for the customers and vendors. how to cerate account symbols for it.. plz any body tell me the accounting entries or the screen shots for it.
    my id is ashokchandra(under score)n at sat(haifen)infotech(dot)com
    regards
    ashok

    hi,
         A/R, A/P Balance interest  calculation already account symbols Create button is available.
    regards,
    janakiram
    Edited by: janaki ram on Sep 30, 2008 11:08 AM

  • Lean ware house management screen shots

    Hi sd gurus,
    now my client is having requirement of lean ware house mgmt ,can any one send me screen shots for configuration process
    to my mail id [email protected]

    Hi Srini,
    Please find the complete notes on Lean Ware House Management System below:
    A09 Lean Warehouse Management: Configuration Guide
    Purpose
    The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
    The Configuration Guide describes how to set up the configuration of a Building Block manually, without the support of automated configuration tools.
    Preparation
    1.1     Prerequisites
    The following building blocks form the basis for all mySAP All-in-One Automotive, High Tech and Industrial Machinery and Components solutions. You only have to install these building blocks once.
    Building Blocks     Comment
    Baseline Building Blocks (Layer 0)     
    J00 - Essential Information     
    J02 - Organizational Structure     
    J03 - Financial Accounting     
    J08 - Controlling     
    J05 - Materials Management     
    J04 - Sales and Distribution     
    Baseline Building Blocks (Layer 1)     
    J06 - Production Planning and Controlling     
    J07 – Quality Management     
    J18 - Product Cost Controlling     
    J19 – Batch Management     
    J20 - Cost Object Controlling – Make-to-Order     
    J21 - Cost Object Controlling – Make-to-Stock     
    J17 - Profitability Analysis     
    J14 - Human Capital Management     
    J09 - Travel Management     
    Industry generic Building Blocks     
    E04 - Supplement Settings     
    E05 - Master Data HT / IM&C     
    Configuration
    1.2     Lean WM Basic Settings
    1.2.1     Defining Control Parameters and Number Ranges for the Warehouse Number &#61664;Defining Control Parameters for the Warehouse Number
    Use
    A warehouse number is an organizational unit in Logistics, which organizes the company from the perspective of Warehouse Management.
    In the Warehouse Management System, you can define a variety of control parameters at warehouse number level.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM &#61507; Define control parameters and number ranges for the warehouse number &#61664;Define control parameters and number ranges for warehouse no.(double click)
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field.
    Table V_T3002
    Field name     Value     R/O/C     Description
    Whse number     L01     R     
    Warehouse no. description     Lean WM BP01     R     
    Weight unit     KG     R     
    Volume unit               
    Default UoM     K     R     
    Time unit/performance data               
    Lean WM active     X     R     
    Link to subsystem active               
    Performance data               
    Transfer order     01     R     
    Group number     01     R     
    1.2.2     Defining Storage Type
    Use
    A warehouse number is subdivided into a variety of storage types. A storage type is defined by its physical or organizational features (for example, high rack storage area, bulk storage, and goods receipt areas).
    A storage type has a short description rather than an address.
    Before you can implement Lean WM, you must configure the following settings:
    1.     Assign a (newly defined) storage location to a warehouse number.(This step is defined by step 3.12 Control Plant / Storage Location / Warehouse Number Assignment
    2.     You should set up at least three storage types:
    &#61692;     a storage type (that will be used as a source storage type) with one or several fixed storage bins
    &#61692;     a goods issue area (as destination storage type) for deliveries
    &#61692;     an interim storage area for differences
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Storage type
    Transaction Code     SM30
    2.     Find the  Field Name and input the relative value into the field
    Table V_T3012
    Data record 1:
    Field name     Value     Sub-screen
    Whse number     L01     
    Warehouse no. description     Lean WM BP01     
    Storage type     001     
    Storage type name     Fixed bin storage     
    Stock plcmt requires confirmation          for putaway control
    Unit of measure type srch          
    Stock rmvl requires confirmation          for picking control
    Unit of measure type srch          
    Data record 2:
    Field name     Value     Sub-screen
    Whse number     L01     
    Warehouse no. description     Lean WM BP01     
    Storage type     916     
    Storage type name     Shipping area deliveries     
    Stock plcmt requires confirmation          for putaway control
    Unit of measure type srch          
    Stock rmvl requires confirmation          for picking control
    Unit of measure type srch          
    Data record 3:
    Field name     Value     Sub-screen
    Whse number     L01     
    Warehouse no. description     Lean WM BP01     
    Storage type     999     
    Storage type name     Differences     
    Stock plcmt requires confirmation          for putaway control
    Unit of measure type srch          
    Stock rmvl requires confirmation          for picking control
    Unit of measure type srch          
    Data record 4:
    Field name     Value     Sub-screen
    Whse number     L01     
    Warehouse no. description     Lean WM BP01     
    Storage type     902     
    Storage type name     IN-ZONE     
    Stock plcmt requires confirmation          for putaway control
    Unit of measure type srch          
    Stock rmvl requires confirmation          for picking control
    Unit of measure type srch          
    1.2.3     Defining Doors
    Use
    In a WM-managed warehouse, you can define dock doors (also known as doors or gates). A door is a location where the goods either arrive in the warehouse or leave it.
    You can assign different functions to a dock door, for example:
    Goods receipt
    Goods issue
    Other transactions such as cross-docking and flow-through
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664;&#61472;Define Doors
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T30B
    Field name     Value     R/O/C     Description
    Whse no.     L01     R     Warehouse number
    Door     A01     R     Door for warehouse number
    Text for door     Door A01     R     Text for door
    Staging area               
    Matl stag. area txt               
    GI indic.     X     R     Goods issue indicator
    GR ind     X     R     Goods receipt indicator
    CD ind               Cross-docking indicator
    FT ind               Flow-through indicator
    1.2.4     Defining Material Staging Areas
    Use
    A staging area is an interim storage area for goods that have been received from goods receipt and afterwards need to be transferred into the warehouse.
    It is also an interim storage area for goods that were picked in a warehouse and are to be loaded for goods issue through loading ramps or doors.
    You can assign different functions to a staging area:
    •     Goods issue
    •     Goods receipt
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Material Staging Area
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T30C
    Field name     Value     R/O/C     Description
    Whse no.     L01     R     
    Staging area     A01-01     R     
    Matl stag. area txt     Zone 1     R     
    Door     A01     R     Door for warehouse number
    Text for door     Door A01     R     
    GI ind     X     R     Goods issue indicator
    GR ind     X     R     Goods receipt indicator
    CD ind               Cross-docking indicator
    FT ind               Flow-through indicator
    HU ind               Handling unit indicator
    1.2.5     Defining Picking Area
    Use
    A picking area is an object within a storage type that groups together storage bins for purposes of stock removal.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664;&#61472;Define Picking Area
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T30A2
    Data record 1:
    Field name     Value     R/O/C     Description
    WhN     L01     R     Warehouse number
    STy (storage type)      001     R     
    PAr (Picking area)     001     R     
    Picking area name     Picking area 1     R     
    Data record 2:
    Field name     Value     R/O/C     Description
    WhN     L01     R     Warehouse number
    STy (storage type)      001     R     
    PAr (Picking area)     002     R     
    Picking area name     Picking area 2     R     
    1.2.6     Defining Transfer Type
    Use
    In Lean WM, the transfer type "A" (stock removal) is required for movement type control.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Transfer Type
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T333A2
    Field name     Value     R/O/C     Description
    WhN     L01     R     Warehouse number
    Transfer type     A     R     
    Text f. shipment type     Pick     R     
    1.2.7     Defining Movement Types
    Use
    The SAP R/3 System uses movement type to process movements in Inventory Management (for example, goods receipt for a purchase order or goods issue to a cost center). When the system recognizes a movement as being relevant for Warehouse Management, it assigns this movement to a WM movement type by means of a table.
    The movement type for the Warehouse Management System provides the information required for stock removals or picking:
    &#61692;     Interim storage bin
    &#61692;     Fixed bin coordinate
    &#61692;     Control indicator for processing, confirming, and printing transfer orders
    &#61692;     Confirmation info
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Movement Type
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T3332
    Data record 1:
    Field name     Value     R/O/C     Description
    Warehouse number     L01     R     
    Warehouse no. description     Lean WM     R     
    Movement type     255     R     
    Movement type description     Goods Issue general     R     
    Src     001     R     
    Src Stor. Bin               
    Dest     916     R     
    Dest Stor. Bin               
    Transfer type     A     R     
    Text for transfer type TRATX     Pick     R     
    TO creation screen     2     R     
    Scr. TO confirmation     2     R     
    Manual TO creation not allowed               
    Transfer priority               
    Print code               
    TO item can be confirmed immed.               
    Propose confirmation               
    Data record 2:
    Field name     Value     R/O/C     Description
    Warehouse number     L01     R     
    Warehouse no. description     Lean WM     R     
    Movement type     601     R     
    Movement type description     Picking by delivery note     R     
    Src     001     R     
    Src Stor. bin               
    Dest     916     R     
    Dest Stor. bin               
    Transfer type     A     R     
    Text for transfer type TRATX     Pick     R     
    TO creation screen     2     R     
    Scr. TO confirmation     2     R     
    Manual TO creation not allowed     X     R     
    Transfer priority               
    Print code     02     R     
    TO item can be confirmed immed.     X     R     
    Propose confirmation               
    1.2.8     Defining Difference Indicator
    Use
    Using the difference indicator, you can classify your differences. This indicator is used in Lean WM for evaluation purposes only.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Difference Indicator
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T3362
    Field name     Value     R/O/C     Description
    WhN     L01     R     Warehouse number
    DiffInd (difference indicator)     X     R     
    Description of difference indicator     Stock difference     R     
    Stor.ty.differences     999     R     
    Diff.bin               
    TO     X     R     
    Source bin               
    1.2.9     Control Plant / Storage Location / Warehouse Number Assignment
    1.2.9.1     Assigning Warehouse No. to Plant-Storage Locations
    Use
    By doing so, system can recognize which storage locations in Materials Management are controlled by the Warehouse Management system (LE-WM); you must assign the plants and the storage location to the warehouse number.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG&#61664;&#61472;Enterprise Structure &#61664;&#61472;Assignment &#61664; Logistic Execution &#61664; Assign warehouse No. To plant/storage Location&#61664;
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table  V_T320
    Field name     Value     R/O/C     Description
    Plant     BP01     R     
    SLoc     0005     R     
    WhN     L01     R     
    1.2.9.2     Control Plant / Storage Location / Warehouse Number Assignment
    Use
    You can control for each combination of plant, storage location, and warehouse number whether Lean WM or standard management of bin inventory is to be selected.
    If you are using Lean WM, you can also specify a picking storage type that is used for creating transfer orders.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Control Plant / Storage Location / Warehouse Number Assignment
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_T3202
    Field name     Value     R/O/C     Description
    Plnt     BP01     R     
    Stor. loc.     0005     R     
    WhNo (Whse number)     L01     R     
    Degree of activation Warehouse Mgmt     1     R     
    Stor.type for picking in Lean WM     001     R     
    1.2.10     
    1.2.11     Assigning Picking Location
    Use
    Assign the picking locations to the combinations of shipping point and storage condition for every plant.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Determine Picking Location  &#61664; Assign Picking Location
    Transaction Code     SM30
    2.     Find the Field Name and input the relative value into the field
    Table V_TVKOL
    Field name     Value     Description
    ShPt     BP01     Plant
    Plnt     BP01     Shipping point/receiving pt
    SC     K1     Storage conditions
    SLoc     0005     Storage location
    1.3     Print Control for Warehouse
    Use
    Print control defines the following:
    •     Which slips are to be printed for the movements (that is, for the transfer orders) within the Warehouse Management System
    •     How these slips are to be printed (that is, which forms are to be used, how many copies are to be printed)
    •     On which printer a slip is to be printed automatically
    And print control manages the print operations of the warehouse. This flexibility involves a certain degree of complexity with regard to the parameterization.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM  &#61664; Define Print control
    Transaction Code     OMLV
    2.     Choose the following button and check the contents
    (Here only the contents of the warehouse no. L01 are listed): 
    2.1     Spool code
    Data Record 1
    Field name     Value     R/O/C     Description
    WhN     L01          R     Warehouse number
    Spool     01     R     Spool request name
    Copies     1          R     Number of copies
    Title     LVS1     R     Spool control data
    Print_immed.     X     R     Print immediately
    Delete_after_print     X     R     Release after output
    NewSplReq__               New spool request
    Data Record 2
    Field name     Value     R/O/C     Description
    WhN     L01          R     Warehouse number
    Spool     02     R     Spool request name
    Copies     1          R     Number of copies
    Title     LVS2     R     Spool control data
    Print_immed.               Print immediately
    Delete_after_print     X     R     Release after output
    NewSplReq__               New spool request
    2.2 sort profile/collective process
    Field name     Rec1     Rec2     Rec3     Rec4     Rec5     Rec6     Rec7     Rec8     Rec9
    WhNo_(Whse_number)     L01     L01     L01     L01     L01     L01     L01     L01     L01
    Sort_profile     1     2     3     4     5     6     7     8     9
    1st_sort_criterion     SPOOI     SPOOI     SPOOI     SPOOI     SPOOI     SPOOI     SPOOI     SPOOI     SPOOI
    Sort_descending_order (1st_sort_criter.)                                             
    Control_break_1st_sort_criterion                                             
    2nd_sort_criterion     LDESI     LDESI     LDESI     LDESI     LDESI     LDESI     LDESI     LDESI     LDESI
    Sortdescending_order (2nd_sort_crit.)                                             
    Control_break_2nd_sort_criterion                                             X
    3rd_sort_criterion     REFNR     REFNR     REFNR     REFNR     FORMI     FORMI     FORMI     FORMI     REFNR
    Sortdescending_order (3rd_sort_crit.)                                             
    Control_break_3rd_sort_criterion     X     X     X     X                         
    4th_sort_criterion     FORMI     FORMI     FORMI     FORMI     LGNUM     LGNUM     LGNUM     LGNUM     FORMI
    Sortdescending_order (4th_sort_crit.)                                             
    Control_break_4th_sort_criterion                         X     X     X     X     
    5th_sort_criterion     LGNUM     LGNUM     LGNUM     LGNUM     VLTYP     VLTYP     VLTYP     VLTYP     LGNUM
    Sortdescending_order (5th_sort_crit.)                                             
    Control_break_5th_sort_criterion                                             
    6th_sort_criterion     VLTYP     NLTYP     VLTYP     TANUM     VLPLA     NLPLA     WERKS     TAPOS     NLTYP
    Sortdescending_order (6th_sort_crit.)                                             
    Control_break_6th_sort_criterion          X     X     X                         X
    7th_sort_criterion     VLPLA     NLPLA     WERKS     TAPOS
         TANUM     TANUM     LGORT          KOBER
    Sortdescending_order_ (7th_sort_crit.)                                             
    Control_break_7th_sort_criterion                         X                    
    8th_sort_criterion     TANUM     TANUM     LGORT          TAPOS     TAPOS     MATNR          VLPLA
    Sortdescending_order (8th_sort_crit.)                                             
    Control_break_8th_sort_criterion                                             
    9th_sort_criterion     TAPOS     TAPOS     MATNR                    CHARG          TANUM
    Sortdescending_order (9th_sort_crit.)                                             
    Control_break_9th_sort_criterion                                             
    10th_sort_criterion               CHARG                    BESTQ
              TAPOS
    Sortdescending_order_ (10th_sort_crit.)                                             
    Control_break_10th_sort_criterion                                             
    11th_sort_criterion               BESTQ                    SOBKZ          
    Sortdescending_order_ (11th_sort_crit.)                                             
    Control_break_11th_sort_criterion                                             
    12th_sort_criterion               SOBKZ                    LSONR          
    Sortdescending_order_ (12th_sort_crit.)                                             
    Control_break_12th_sort_criterion                                             
    13th_sort_criterion               LSONR                    VLTYP          
    Sortdescending_order_ (13th_sort_crit.)                                             
    Control_break_13th_sort_criterion                                             
    14th_sort_criterion               VLTYP                              
    Sortdescending_order_ (14th_sort_crit.)                                             
    Control_break_14th_sort_criterion                                             
    15th_sort_criterion                                             
    Sortdescending_order_ (15th_sort_crit.)                                             
    Control_break_15th_sort_criterion                                             
    2.3 print code
    Field name     Rec1     Rec2     Rec3     Rec4     Rec5     Rec6     Rec7
    WNo___(Warehouse_number)     L01     L01     L01     L01     L01     L01     L01
    PrCd__(Print_code)     01     02     03     11     12     21     22
    Print_code_description                                   
    Find_shipping_data____                                   
    Determine_production_data_                                   
    Form_     LVSTAEINZEL     LVSTALISTE     LVSTOSOLO     LVSTAEINZEL     LVSTALISTE     LVSKOMMIL1
         LVSKOMMIL2
    PTm_(Time_of_printing)________                                   
    Sort_profile     1     1          1     4     1     1
    Combined_print          x               x     x     x
    Spool_data     02     02     01     02     02     02     02
    Label_form               LVSLABELS                    
    Label_spool_code               01                    
    Quantity_of_labels_(Indicator)               2                    
    2.4 assign printer to storage type (LP01 to 001 only)
    Field name     Rec1     Rec2     Rec3
    WhNo_(Whse_number)     L01     L01     L01
    STy__(storage_type)     001     916     999
    Storage_type_description     Fixed bin storage     Shipping area deliveries     Differences
    Printer               
    2.5 assign print code to movement type
    Field name     Rec1     Rec2     Rec3
    WhNo_(Whse_number)     L01     L01     L01
    MvT__(WM_movement_type)     101     255     601
    Movement_type_description     Goods receipt for pur.or.
              Picking by delivery note
    PrCd__(Print_code)     01          02
    2.6 assign print report to warehouse No.
    Field name     Rec1
    WhNo_(Whse_number)     L01
    Warehouse_number_descrip.     Lean WM Plant BP01
    Print_report     RLVSDR40
    2.7 print control multi-processing
    Field name     Rec1
    WhN     L01
    Ref.ty.     L
    Status     2
    Print_prog.     RLKOMM40
    PrCd     21
    Printer     LP01
    1.4     Manual Activity
    1.4.1     Maintaining Number Range Intervals for Transfer Order
    Use
    Maintain number range intervals for transfer order
    Procedure
    In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
    Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM &#61664; Define control parameters and number ranges for the warehouse number &#61664; Maintain number range intervals for transfer orders (double click)
    Transaction Code     LN02
    Check if the internal number range 01 (0000000001-1000000000) has been defined
    Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
    Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
    1.4.2     Maintaining Number Range Intervals for Reference Numbers
    Use
    Reference number range has the following meanings:
    This number identifies a number range to be used for the assignment of sequential numbers for WM reference numbers. Reference numbers are used to create or print a group of transfer orders at one time.
    A sequential number generated by the system for the purpose of multiple processing of transfer requirements and delivery notes.
    The reference number can also be used to print the resulting transfer orders at a later time.
    Procedure
    In this step, you define that, the Number range for Transfer order as 01 and Group number as 01, now you should tell the system how the number range would like for 01 as transfer order and 01 for the group number, for both number range, you may define you own number range, the following information just for reference:
    Access the activity using one of the following navigation options:
    IMG Menu     IMG &#61664; Logistic Execution &#61664; Shipping &#61664; Picking &#61664; Lean WM &#61664;&#61472;Define control parameters and number ranges for the warehouse number &#61664; Maintain number range intervals for Reference Numbers( double click)
    Transaction Code     LN06
    Check if the internal number range 01 (5000000000 - 5999999999) has been defined
    Once you have defined your number ranges, it is extremely difficult to change them afterwards when the objects concerned are filled with data.
    Bear in mind that you will be entering data on a long-term basis. Create your number range intervals accordingly.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

Maybe you are looking for