Quantcast
Channel: SCN : Document List - Enterprise Resource Planning (SAP ERP)
Viewing all 131 articles
Browse latest View live

Split Production Order

$
0
0

 

Index

 

Introduction..

Configuration Settings.

Step I: Define Order Type dependent parameters (OPL8).

Transactional Setting..

Assumptions:.

Step I: Create Production Version for finish material SPLT_1000 (C223).

Step II: Create Product Cost Collector for finish material SPLT_1000 (KKF6N).

Process Flow Steps.

Step I: Create & save with release production order (CO01).

Step II: Confirm the production order (CO11n).

Step III: Change production Order (T-Code CO02).

Step IV: Confirm production Order (T-Code CO11N).

Step V: Goods Receipt for Production Order (MIGO).

Restrictions.

 

Introduction

 

Order split enables us to split an existing production order, for which processing may have already begun, into two separate production orders. These production orders are then executed separately from a logistics perspective. We might want to perform an order split for the following reasons

·         When a partial lot of a production order has to be handled differently than the rest due to quality reasons, you can create a separate order to do this.

·         If capacity bottlenecks occur, the portion of the order quantity that is required immediately can be processed separately.

·         The material availability can only be confirmed for part of the order quantity. You split the order to create an order with full material availability.

·         If the required date for a partial quantity of the finished material has changed, this portion can be split off in a different order.

·         If a production order cannot be completed on time, you can split the order to reduce the order quantity. The reduced order quantity then requires less time to produce.

 

When we split an order, we split off part of the order quantity (split quantity) of a production order (parent order) from a certain operation of the standard sequence (split operation). The quantity that is split off is produced in a separate production order (child order). In the process, the operations from the split operation onwards are copied from the parent order to the child order, along with the assigned material components. The system automatically recalculates all the quantities affected by the order split, as well as dates at header, operation, and component level.

In this article process steps are explained with an example considering following assumptions.

·         There is only a standard sequence in use and no alternative sequences.

·         There is no in process inspection.

·         No Serial Number assignment.

 

Configuration Settings

 

Step I: Define Order Type dependent parameters (OPL8)

 

SPRO --- Production --- Shop Floor Control ---Master Data --- Order --- Define order type-dependent parameters

 

For required order type, Activate check box Cost collector and define Default Rule as “PP2” - Production Mat. Period. Settlement

 

OPL8.jpg

 

Transactional Setting

 

Assumptions:

 

Following are has been created already:

 

1. Finish Material SPLT_1000 – with selection method 3 (MRP 4 view)

 

Create MMR.jpg

2. Bill Of Material

3. Routing

 

Step I: Create Production Version for finish material SPLT_1000 (C223)

 

Production Version.jpg

 

Step II: Create Product Cost Collector for finish material SPLT_1000 (KKF6N)

 

Product Cost collector.jpg

Product Cost collector screen 2.jpg

 

Note: There should be order type with order category as 05

 

Process Flow Steps

 

Step I: Create & save with release production order (CO01)

 

Create production order for SPLT_1000 material with order type PP01 and with quantity 100 EA.

 

Prod order 1.jpg

Prod order 2.jpg

 

Out of total four operations, confirm first two operations with actual operation quantity.

Order split is allowed with following system status:

 

·         Header Status: Partially released, released, partially confirmed.

·         Operation Status of the split operation and all successors: Created, released, partially confirmed

 

The order split is not allowed with the following status:

 

·         Header status: Created, delivered, finally confirmed, locked, technically complete, closed, deletion indicator set

·         Operation status of the split operation and all successors: Finally confirmed, dispatched, partially dispatched, capacity split, capacity requirement assigned, capacity requirement partially allocated

·         Operation status of the split operation: Deleted.

 

Step II: Confirm the production order (CO11n)

 

Confirm Operation 0010 & 0020 as below:

Confirmation.jpg

 

Confirmation 2.jpg

Step III: Change production Order (T-Code CO02)

 

Split the production order with split quantity 37 EA from operation 0030.

In production order operation overview, select the operation 0030 and go to functions menu and click on split order.

 

Split Order.jpg

 

Enter required split quantity in split quantity field. Here we can select different order type for child order. And further system will also allow us to schedule the child order with different dates.

After entering all parameters, execute split (click on split order execute button).

System will create a child order with specified parameters and it will be displayed along with parent order in split hierarchy.

The split hierarchy displays the dependencies between the parent and child orders in an overview tree. During order maintenance, the split hierarchy and the selected order from the split hierarchy are displayed. We can navigate to any order in the split hierarchy (tree structure).

Orders (including child orders) can be split several times. The dependencies can be seen in the split hierarchy.

Split Order parameter.jpg

Splited Order.jpg

After splitting Order, system will set the status SPLT (Split) at header and operation levels for parent order and split qty. as expect yield variance.

Operation qty. will be reduced to 63 PCs. from operation 0030 to the succeeding operations.

System will set the status CSPL (created by splitting) at header level for child order (1000315). All successive operations from split operation (including split operation) will be copied to the child order along with all assignments (for example material components, PRTc etc...)

For child order we can check the reference order (1000314) in controlling data tab.

Display Order.jpg

Display Order 1.jpg

Display Order 3.jpg

Display Order 4.jpg

 

Step IV: Confirm production Order (T-Code CO11N)

 

Confirm the rest operation of parent production orders i.e 1000314. You will found Yield quantity as 63     (Because Parent order quantity – Spitted Quantity i.e 100 – 37 = 63)

Confirm child order 1.jpg

Confirm child order 2.jpg

 

Likewise Confirm Child order 1000315

 

Confirm child order 3.jpg

 

Step V: Goods Receipt for Production Order (MIGO)

 

Perform Goods receipt for both orders with their respected yield quantities.

In this case delivered quantity for the parent order (1000314) is 63 EA. For child order (1000315) final delivered quantity is 37 EA.

 

GR.jpg

GR 1.jpg

 

Go to T-code CO03 to see Reference order of Child order

 

Reference.jpg

Restrictions

 

The following restrictions apply to the order split:

 

·         The parent order and child order must both be settled to the same product cost collector

·         We cannot read master data for the orders in a split hierarchy

·         Orders in a collective order cannot be split

·         Orders of a split hierarchy cannot be supplemented with a sub tree

·         The parent and child order must both have the same header material

·         We cannot perform confirmations at order header level

·         The batch where-used list is not updated during order split.


Dependencies of Role/Profiles

$
0
0

Dependencies of Role/Profiles

Role/Profiles can be calssified in the below four types Dependencies   :

Ø  All User Dependency

Ø  Basis Dependency

Ø  Job dependency

Ø  Role-Profile Dependency

 

All User Dependency :

These are the roles/profiles which are required by all the user in that category like user group , system or in that particular client .

User are created in the respective systems with the respective authorization roles/profiles .

 

 

All user dependencies are again further divided into three  categories :

“All internal user”,

“All External User”

“All User”

All Internal User: These include the Roles/Profiles for the members within the organization .

All External User: These include the Roles/Profiles which are classified for the external employees to the company e.g. : Contract Employees , Vendors etc .

All User: This include the Roles/Profiles for all the users ; irrespective of internal or external Uers to an organization .

 

Basis Dependency :

User will get such roles/profiles when they get other authorizations for the systems, e.g. via ARM request .

 

 

Same way like ‘All User Dependency’  ; Basis Dependency have “All internal user”, “All External User” or “All User” .

 

Job Dependency :

This include the Roles/Profiles which are given to the user on the basis of their job requirement.

Job related assignments are done based on organizational assignments of the user. Possibilities are:

a.      Cost Center assignment

b.      Company Code assignment

c.       Job-ID assignment

 

 

Same way like ‘All User Dependency’  ; Job Dependency have “All internal user”, “All External User” or “All User” .

 

Role-Profile Dependency:

Profile-Role dependencies show a dependency base on a source role/profile.

 

This employs for the Roles/Profiles which are given to the user in correlation with the role required by the user.

 

Thus depndencies serve the purpose of corelation of the roles/profiles and the segregation of the user role/profile assignment and their requirements .

IM, WM and EWM - selecting the right solution

$
0
0

This article gives a brief overview of the functionalities available in IM, WM and EWM and then a comparitive ananlysis of these three to select the suitable solution.

Finding and Navigating SAP Best Practices

Easy Steps for LSMW Creation

$
0
0

Overview of lsmw program


LSMW is a powerful tool for data migration. It has mainly four ways of data input from legacy system to SAP; Standard Batch/Direct Input, Batch Input recording, BAPI and IDoc. The source of data is, to a large extent, excel sheets and its other filetypes (csv, tab delimited etc).

 

This document will be discussing only the Batch Input recording way of data migration. Batch input recording is the most flexible of all the different methods of data input. It gives the option of recording a particular Tcode or Tcodes while system registers the various fields navigated during recording. After the record is complete, the same Tcode or Tcodes can be run as a batch session with the source of data as an excel sheet.

 

NB: The document is made to demonstrate the recording and subsequent upload of asset master (Tcode AS01). The document can be used for any kind of program creation; material master, Vendor master, posting transactions etc

 

Step

Action

1.

Execute the Tcode LSMW

 

1.gif

Step

Action

2.

Provide a name of the project and click create

3.

Provide a description for the project. Then enter the subproject and finally the object

2.gif

Step

Action

4.

Click the execute button

5.

From the list of operations, select the first, “Maintain Object Attributes” and click execute (or just double click on the line)

 

3.gif

 

Step

Action

6.

Select the radio button for ‘Batch Input Recording’ and click on ‘Recordings Overview’

 

4.gif

Step

Action

7.

Click the create button, and provide the name of the recording and click ‘continue’

 

5.gif

Step

Action

8.

In the ‘Transaction code’ window, provide the Tcode. In this case it is ‘AS01’ and click continue

 

6.gif

Step

Action

Note

The system has started recording and any field input in the next steps will be recorded as an input field. Also try to complete recording without encountering an error.

Step

Action

Note

The next few steps will be exactly the creation of an Asset master record. To keep the document small, only the last screen is captured that ends the recording.

Step

Action

9.

Click on the save button after all the required entries are given for asset master record creation. This ends the recording and system takes back to LSMW

 

7.gif

 

Step

Action

10.

From the recording system created, edit the necessary field by double clicking on each.

 

8.gif

Step

Action

Note

Provide a name and description for the field and note carefully that the ‘Default Value’ field should be left blank if the entry varies in each record from the upload file. Ie, in the case of Asset master creation, the asset class varies so should be left blank. However, if you are creating a upload for only ABCD co.code assets, the default value should be filled in as ABCD since it is constant across the upload.

Also note that unnecessary fields can be deleted.

 

Step

Action

Note

Similarly, edit every field that the system recorded and click Save. Then click back thrice.

 

9.gif

Step

Action

Note

It is important to make sure that the recording we made in the previous step is populated in the ‘Recording’ field. If you don’t find there, press F4 and system will populate it. If you move to the next step without making this point sure, there will be error later.

 

Step

Action

11.

Click save and press back once. Now select the second step from the list and click execute (or double click)

12.

Provide a Source structure name and description.

 

10.gif

Step

Action

13.

 

Click save and click back. From the list of operations, select the third ‘Maintain Source Fields’ and click execute.

14.

Place the cursor on the source structure ‘MAS_ASSET’ and from the ‘Source Fields’ drop down at the top left corner, select ‘Table Maintenance’

11.gif

Step

Action

15.

Provide the list of fields that was created as part of recording. The ‘Field Name’ is the name of the field, Type is the type of input; Character, numeric, alphanumeric etc, Length is the length of the input field and finally field description.

Click save, press back. Again click save and then click back

 

12.gif

 

13.gif

Step

Action

16.

From the list of operations, select the 4th‘Maintain Structure relations’ and click execute

 

14.gif.

Step

Action

Note

Since a mapping is already made between the target structure and source structure, there is no action in this step. You could press save and press back.

 

Step

Action

17.

From the list of operations, select the line 5 ‘Maintain Field Mapping and conversion Rules’ and click execute

 

15.gif

Step

Action

Note

This structure is the target structure. The step is very important because a mapping is established between target strcutre field and source strcutre fields. Also, this is the step at which the upload excel file should be created.

Just create an excel file with the columns as the above target structure fields.

Step

Action

18.

Place the cursor on the first field and click on ‘Source Field’. From the list of source fields, select correctly (double click) that field which would be mapped to the target field. For eg: the first target field in the structure is ASSET_CLASS. Since ASSET_CLASS should be mapped to the source field ASSET_CLASS, map each other.

 

16.gif

Step

Action

Note

Similarly assign every field in the target structure to the source structure fields. Note that if there are constant fields, usethe ‘Constat’ button to assign a constant value.

Step

Action

Note

After the mapping is complete, click on save and click back

Step

Action

19.

Operation 6 ‘Maintain Fixed Values, Translations, User Defined Routines’ can be ignored

20.

Select operation 7 ‘Specify Files’ and click execute

 

17.gif

 

Step

Action

21.

Place the cursor on ‘Legacy Data’ and click on ‘create’

18.gif

Step

Action

Note

The excel upload file created should be saved as a ‘Tab delimited’ file. This file location should be given in the previous step.

Step

Action

22.

Place the cursor on ‘Legacy Data’ and click on ‘create’

23.

Make sure the ‘Tabulator’ radio button is selected in the ‘Delimiter’ section. This is because the file is ‘Tab delimited’

24.

Make sure the ‘Field Names at start of File’ should be selected in the ‘File structure’ section. This is because the first row in the upload file is column name and the actual data starts only from the second line in the file

19.gif

20.gif

Step

Action

25.

Click on save and click back

Note

Many times you might error about the length of ‘Converted Data and/or ‘Imported Data’. It just means that the length of file name of Imported data and/or converted data is longer than 45 characters. All you have to do is to double click on the line and reduce the file name.

 

Step

Action

26.

Select the operation 8 ‘Assign Files’ and just click save and click back

27.

Select the operation 9 ‘Read Data’ and click execute. Click execute in the next screen.

21.gif

22.gif

Step

Action

28.

Click back twice

29.

Select the operation 10 ‘Display Read Data’ and click execute.

30.

Click continue in the ‘Display Read Data’ pop – up box

 

23.gif

Step

Action

31.

Randomly select some records and click on it. Make sure that the target strcture data format and fields are correct. If they are not correct, you will have to re-do the target strcture part again. But if you did all the steps correctly till now, it will not give a problem.

24.gif

Step

Action

32.

Select operation 11 ‘Convert Data’ and click execute

33.

Click execute again in the next screen

 

25.gif

Step

Action

34.

Click back twice

35.

Select the operation ‘Display Converted Data’ and click execute

36.

Select continue in the ‘Display Converted Data’ pop-up box

Step

Action

37.

Randomly select some records and click on it. Make sure that the mapping is correct. Ie, character, fields etc are correctly mapped to the target structure.

38.

Press back button twice

39.

Select the operation 13 ‘Create Batch Input Session’ and click execute

26.gif

 

Step

Action

40.

Click on execute

 

27.gif

Step

Action

41.

Select the operation 14 ‘Run Batch Input Session’ and click execute

42.

Select the batch session and click the ‘Process’ button

43.

From the ‘Process Session **’ pop-up, select the processing mode. If the mode is background, system will run pulling the information from the excel sheet and run the transaction that number of times as much data in upload file, in the background.

If you run in ‘Display errors only’ system will throw any error it encountered during the task and will proceed only after you manullay correct.

And finally ‘Process/foreground’ will mandate you to press the return key for every screen action. Use this only for very few records. Using this for an upload file of 10000 records will be a very bad idea.

 

After selecting the mode, click on the button ‘Process’

 

NB: For this demonstration, I ran in Background.

28.gif

 

Step

Action

44.

This will schedule the batch session in background. Analyze the session to see it resulted in any error. If you notice error, correct it

ST03 -: No System Load data available

$
0
0

In Transaction ST03 , you encounter No system load data available. The same is the case with the STAD transaction.

 

1.PNG

 

Even the scheduling of the hourly job SAP_COLLECTOR_FOR_PERFORMANCE does not help.

 

Check the output of the following report to see if there are any inconsistencies in the Time Zone Settings -:

TZONECHECK -> Check Time Zone Data for Consistency

TZCUSTHELP -> Troubleshooting Support for Time Zone Settings

 

Please refer the note which would help in resolving the issue -:

1888095 - ST03/ST03N gets popup "No system load data available".

 

Transaction -: STZAC

 

2.PNG

On clicking Yes -: You get the following

3.PNG

Reason can be verified in SCC4 transaction as can be seen below that the client 000 is set to No Changes allowed. Change this setting for the time to Changes Without Automatic Recording.

 

4.PNG

Change this setting -: SCC4 -> Click the change icon -> This display the information -:

 

5.PNG

Proceed . Then select the client 000 -> Goto -> Details and change it as displayed below.

 

6.PNG

Save the changes and again use the transaction STZAC and change the System Time Zone and User’s Default Time Zone accordingly and save the changes. Please revert to No Changes allowed for client SCC4 after the changes to System Time Zone and User's default Time Zone has been done successfully.

 

----------------------------------------------------------------------------------------------------------------------------------------------------------

Details of scheduling the Job in SM36 -:

7.PNG

Click on Start Condition and set immediate, Periodic

9.PNG

Set the hourly periodic value -:

12.PNG

Save. No Variant.

11.PNG

Save.

 

 

 

 





Trading partner functionality in accounting document

$
0
0

Hope we all are aware about trading partner functionality from SAP FICO point of view, which is mainly used for recording and reporting of inter-company transactions.

 

Trading partners are updated in GL, Customer and Vendor master and majorly used in customers and vendors. Some clients may use trading partner in an indirect way to update in GL transactions thereby not updating in GL master through exit or substitutions.

 

Trading partner can be inherited or derived from master or can be entered manually in transactions. Updation of trading partner is being controlled through relevant document type configuration in SAP.

 

Lets take an example of the document type configuration:-

 

Its being controlled through two main checkboxes in document type configuration (OBA7 transaction code) namely, "Inter-company postings" and "Enter Trading partner" checkboxes

 

a) If "Inter-company postings" checkbox is set and "Enter Trading partner" is not set

 

Functionality: Trading partner is derived from master data and no manual entry is possible in line item / transactions. Here trading partner must not be unique in a document.

 

b) If "Inter-company postings" checkbox is not set and "Enter Trading partner" is set

 

Functionality: Trading partner can be manually entered in line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.

 

c) If both "Inter-company postings" and "Enter Trading partner" checkboxes are set

 

Functionality: Trading partners are derived from master data and can also be entered manually in the line item / transaction in the "More Data" screen. Here trading partner must not be unique in a document.

 

d) If both "Inter-company postings" and "Enter Trading partner" checkboxes are not set

 

Functionality: Trading partner can be manually entered in a line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.

 

 

In short, both (b) and (d) represents the same functionality and it depends on each of the document type configuration with the business process involved.

 

Error message: We normally get error message "Consolidated Companies are different" Message F5080 in either posting or clearing transaction codes.

 

I faced this problem specifically in clearing transaction codes especially with AB document type where one of the document contains trading partner and other doesnt contains blank or different trading partner.

 

Solution: For example, in AB doc type, "Enter trading partner" is set but "Inter-company postings" checkbox is not set. The above error message can be solved by also ticking "Inter-company postings" so that even different trading partners or blank trading partner field will be cleared off without any error message.

 

Also attached herewith document with screenshot for reference.

PGI Button grey-out (Disabled) during initial VL01N in SIT scenario

$
0
0

Descriptioin

In VL01N delivery creation, you found the Post GI button was grey-out (disabled). The button is only available after checking the delivery in VL02N.

It doesn' happen for TAN item category but only happens in SIT scenario (schedule line cateogyr NU / movement type 687).

 

Resolution

This is the standard behavoir for PGI buttion grey-out in VL01N in case of SIT scenario in sales order. It is not allowed to PGI when creating delivery in such a case.

 

Technical reason

The note 1557257 is the reason why "post GI" button is grey-out.

In SIT scenario, if you create delivery and PGI in one step, error M7242 might be triggered.

To solve this error, note 1557257 prohibts posting GI in tcode VL01n (in SIT scenario). This is why the PGI button is grey-out.

sit goods issue button gray.PNG

Relevant SAP Note

SAP Note 1557257: Error message M7 242 when posting SIT movements

 

Relevant document

Wiki page http://wiki.scn.sap.com/wiki/x/GgiEFQ  


How to Download and Upload SAP Queries,Infosets and User Groups to another client or System[QAS,PRD]?

$
0
0

How to Download and Upload SAP Queries,Infosets and User Groups to another client or System[QAS,PRD]?

 

Downloading SAP Queries,Infosets and usergroups could be a bit daunting at first,but nevertheless it is quite a useful skill to have in your arsenal. SAP Queries can be divided into 2 parts called work areas:

(a)Standard Area(client-specific)

(b)Global Area(cross-client)

 

Any query created in the standard area is available to a particular client in the sap system. For instance in the Development system with client 100.

Any Query created in the Global Area is available across all clients of given system. For instance in the Development system,which has clients 100,200,300 etc.

Most of the SAP Standard Queries available under 'Information System' nodes belong to the Global Area,which usually used for SAP created Query Reports. Most custom SAP Query reports are created in the Standard Area.

 

The following steps would be required in order to download and upload SAP Queries:

 

01 - Identifying the list of reports to be downloaded(T-code = SQ01):

> To seek out all queries relevant to your user group first enter in the transaction 'SQ01' in the command field.

> use the menu path:

        Environment > Query Areas > Standard Area(client-specific)

> Now click the other user group button[ ico_Other User groups Button icon.png  ] on the extreme left of the application toolbar or use the key board shortcut of 'Shift + F7'.

Clicking it will bring in all user groups associated with the the selected area and select your specific user.

> Once the user group has been selected it brings in all the Queries created by your specific user group.

 

01 - Finding list of SAP Query Reports to be downloaded using SQ01
01_Finding_listof_SAP_Query_reports_tobe_downloaded_using_SQ01.png

 

 

> Copy the names of all the reports that you want to download,by selecting one of the columns and pressing the 'Ctrl + Y' shortcut to select values of a specific column. ideally copy and paste them in an excel sheet.

> Also copy the names of the infosets for the reports to be downloaded,by following the same procedure as carried out by copying the names of the reports.

 

02 - Finding list of SAP Query infosets to be downloaded using SQ01
02_Finding_listof_SAP_Query_iinfosets_tobe_downloaded_using_SQ01.png

 

 

[NOTE]:

> First download the user groups,associated with the Queries and Infosets.

> Secondly download the Infosets

> Lastly,download the relevant queries.

> Do keep in mind that all infosets associated with the reports must also be downloaded.

> In SQ01,you can also find the name of the infoset associated with it as well. Which is shown in the form of an alv like list,once you have selected your user group,as mentioned above.

> Do remember the work area in which you have created your user group(Standard Area or Global Area),as all queries are associated with your usergroup,and if the correct work area is not selected,the list of queries associated with it won't be shown.

 

For finding the list of all SAP Queries associated with an Infoset:

> There is a query mechanism in SQ02,that allows you to fetch all the reports associated with a particular infoset. Right click the infoset name and choose the 'Queries for Infoset' option,this will show a list of SAP Query reports that are using this selected infoset.

 

 

03A-For finding SAP Queries associated with a given infoset in SQ02
03A_For_finding_SAP_Queries_associated_with_a_given_infoset_in_SQ02.png

 

 

03B-SAP Queries associated with a given infoset in SQ02
03B_SAP_Queries_associated_with_a_given_infoset_in_SQ02.png

 

 

02 - Procedure for Downloading Usergroups, SAP Query Reports and Infosets:

There are two ways in which you can download Usergroups,SAP Queries and Infosets:

(A)Using the transaction SQ02 and using the menu path:

     Environment > Transports


 

04A - Menu Path for downloading Sapquery and SAP Infoset
04A_menu_Patha_for_downloading_sapquery_and_SAP_Infoset.png


 

                                                  [OR]

 

you can open a program named 'RSAQR3TR' in transaction 'SE38'(ABAP Editor),by copying this name and pressing the 'F8' key to execute this program.

 

04B - SAP Standard Program downloading Sapquery and SAP Infoset[Alternate]
04B_SAP_Standard_Program_downloading_sapquery_and_SAP_Infoset[Alternate].png

 

 

This will bring the 'SAP Query Transport Tool',a utility for performing transports of mentioned objects.

 

> In the 'Transport Action Selection' area,select the 'Download' radio button. Next check the

'Overwriting allowed(only with import/upload/copy)' checkbox. Finally uncheck the 'Test run' checkbox in this area. If you want to transport variants created by the users as well,you can check one of the query variant option checkboxes.

 

> Now in the 'Transport Option Selection' area,select the radio buttons based on the following sequence as mentioned before:

 

(A)User Group

Select the 'Transport user groups' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'user groups' field,enter in one or more user groups to be downloaded.

 

04C(1A) - Downloading User Groups
04C(1A)_Downloading_UserGroups.png

 

04C(1B) - Usergroup Download Log
04C(1B)_Usergroup_Download_Log.png

 

(B)Infosets

Select the 'Transport Infosets' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'Infosets' field,enter in one or more Infosets to be downloaded.

 

 

04C(2A) - Downloading an Infoset
04C(2A)_Downloading_Infoset.png

 

04C(2B) - Infoset Download Log
04C(2B)_Infoset_Download_Tag.png

 

(C)SAP Queries

Select the 'Transport queries' radio button,in the 'Import Option' field enter in 'REPLACE' and in the 'Usergroups' field,enter in one or more usergroups and in the 'Queries' field.

 

04C(3A) - Downloading SAP Query
04C(3A)_DownloadingSAPQuery.png

 

04C(3B) - SAP Query Download Log
04C(3B)_SAPQuery_Download_Log.png

 

You will need add in the list of all User groups, Infosets and SAP Queries names already copied in the first step in an excel sheet. Just copy and paste each of them in their respective fields.

 

> Finally,once you have provided the selection criteria above,click the execute button,which will prompt you to download the provided SAP Queries and Infosets into an archive file with no extension. Do keep in mind that this archive will be used for uploading  these on a target  client.

[NOTE]:

> In case you don't see the topmost set of radio buttons for downloading or uploading SAP Query related objects via the menu path mentioned above in transaction SQ02,you can use the program version of the Download utility(RSAQR3TR).

 

03 - Procedure for Uploading Usergroups, SAP Query Reports and Infosets:

The method for uploading all query related objects  to the target system or client,uses the same mechanism as that of downloading these objects. The only difference is that you will need to select the 'Upload' radio button in the 'Transport Action Selection' area in the SAP Query Transport tool. For accessing the SAP Query Transport tool through two different mechanisms,please the refer the section '02 - Procedure for Downloading Usergroups, SAP Query Reports and Infosets'  in this document. For User groups you will need to provide the User group name,for Infosets you will need to provide infoset names and finally for Queries you will need to provide usergroup name as well as the SAP Query names in the fields provided. When you execute the Transport utility by pressing the 'Execute' button [or] pressing the F8 key,you will be prompted to provide the file name for the given object which you would like to upload to. Do remember that you need to log into the target system to complete it.

 

(A)User Group

 

05(1A) - Uploading User Groups
05(1A)_Uploading_UserGroup.png

 

05(1B) - Usergroup Upload Log
05(1B)_Upload_Log.png

 

 

(B)Infoset

 

05(2A) - Uploading an Infoset
05(2A)_Uploading_Infoset.png

 

05(2B) - Infoset Upload Log
05(2B)_Infoset_Upload_Log.png

 

 

(C)SAP Query

 

05(3A) - Uploading SAP Query
05(3A)_Uploading_SAP_Queries.png

 

05(3B) - SAP Query Upload Log
05(3B)_SAPQuery_Upload_Log.png

 

and finally if all the steps have been successfully followed,you will find them uploaded to any of the targeted systems. In my case,on QAS server. See the screenshot below.

 

06 - SAP Query Successfully Transported to QAS
06_SAPQueryReports_Uploaded_to_QAS(Final).png

 

I have also attached the sample sap user group,infoset and queries backup as were demonstrated throughout this document. These could found individually attached with the following names 'z_sap_queries.zip','zfj_infoset.zip' and 'zfj_usergroup.zip'. Just extract each of them to upload them via SQ02.

 

Some Caveats for SAP Query Uploads to Work:

> Lets say you have not added a user(An SAP User) to a user group from where you want to access you sap query related objects. You should add it in the SAP User group from the SQ03 transaction.

 

> Make sure that all SAP Queries have been re-generated and they don't have any errors. These could be achieved by first selecting the SAP Query in SQ01 and going to the menu path:

     Query > More Functions > Generate Program

 

Secondly,you can also adjust your query to reflect newer changes in the SAP Info set associated with it. This can be achieved by going to the menu path:

     Query > More Functions > Adjust

 

Do keep in mind that if there are any errors in you SAP Query objects,they wont be uploaded successfully to the targeted system.

 

[NOTE]:

> These caveats should be followed on the Source Client on which you have created all your SAP Query related objects.

 

Legal

Fahad Javed's Copyrights

All Screen Shots taken,Fahad Javed's Logo are copyrights © 2010-2013 Fahad Javed. All Rights Reserved.

All the material written is a labour of hardwork carried out by the author. Kindly don't copy this material for commercial purposes. If a link is provided do provide the accredition to the author as follows:'© 2010-2013 Fahad Javed. All rights reserved.'.

All the terms used are copyrights of SAP AG  © 2013 SAP AG. All rights reserved. See the section 'SAP - Copyrights and Trademarks' for further details.

 

SAP - Copyrights and Trademarks

© 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is  an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Trading partner functionality in accounting document

$
0
0

Hope we all are aware about trading partner functionality from SAP FICO point of view, which is mainly used for recording and reporting of inter-company transactions.

 

Trading partners are updated in GL, Customer and Vendor master and majorly used in customers and vendors. Some clients may use trading partner in an indirect way to update in GL transactions thereby not updating in GL master through exit or substitutions.

 

Trading partner can be inherited or derived from master or can be entered manually in transactions. Updation of trading partner is being controlled through relevant document type configuration in SAP.

 

Lets take an example of the document type configuration:-

 

Its being controlled through two main checkboxes in document type configuration (OBA7 transaction code) namely, "Inter-company postings" and "Enter Trading partner" checkboxes

 

a) If "Inter-company postings" checkbox is set and "Enter Trading partner" is not set

 

Functionality: Trading partner is derived from master data and no manual entry is possible in line item / transactions. Here trading partner must not be unique in a document.

 

b) If "Inter-company postings" checkbox is not set and "Enter Trading partner" is set

 

Functionality: Trading partner can be manually entered in line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.

 

c) If both "Inter-company postings" and "Enter Trading partner" checkboxes are set

 

Functionality: Trading partners are derived from master data and can also be entered manually in the line item / transaction in the "More Data" screen. Here trading partner must not be unique in a document.

 

d) If both "Inter-company postings" and "Enter Trading partner" checkboxes are not set

 

Functionality: Trading partner can be manually entered in a line item / transaction by choosing Extras menu button -> Trading partner which will be applicable for all the line items in a document. Here trading partner is unique in the document.

 

 

In short, both (b) and (d) represents the same functionality and it depends on each of the document type configuration with the business process involved.

 

Error message: We normally get error message "Consolidated Companies are different" Message F5080 in either posting or clearing transaction codes.

 

I faced this problem specifically in clearing transaction codes especially with AB document type where one of the document contains trading partner and other doesnt contains blank or different trading partner.

 

Solution: For example, in AB doc type, "Enter trading partner" is set but "Inter-company postings" checkbox is not set. The above error message can be solved by also ticking "Inter-company postings" so that even different trading partners or blank trading partner field will be cleared off without any error message.

 

Also attached herewith document with screenshot for reference.

SAP EHP 1…,5,6,7 Activation Process, prerequisite, and Features.

$
0
0

As a part of SAP's ongoing Improvement in ECC 6.0, SAP releases enhancement packages on a regular basis. Read all Business function carefully , Business function shows you in a convenient way and tailored to your current SAP system usage which new business functions relate to your most used business processes.

 

Related SAP useful Link –

 

http://help.sap.com/erp607#section1

 

https://websmp204.sap-ag.de/support

 

  • ((Service market place - Release and upgrade info - Release note - SAP Solution - SAP ERP 6.0 - Enhancement package)

 

1.jpg

2.jpg

 

https://websmp202.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=&_HIER_KEY=501100035870000016962&_HIER_KEY=601100035870000215177&_HIER_KEY=601100035870000240956&

 

3.jpg

4.jpg

 

Find out the Relevant Business function for current business Process


Careful! Only reversible business functions can be deactivated For this reason, activate only required business functions In case of doubt, read the corresponding documentation.


Steps 1 – Go to Documentation

Step 1.1 – check technical data

 

5.jpg

 

Step 1.2 – Check Prerequisite

 

6.jpg

 

If above condition satisfied than go to next step

 

Step 2 - Features

7.jpg

 

Read all features and select which one is useful

 

Steps 3 -   Go to Released note and read that, what effect on Existing data and Existing customization. Make customization setting according to Documentation or Released note.

Step 4– Go to Business function in SAP Dev server

IMG Screen or T. Code SFW5

 

8.jpg

 

9.jpg

 

Read Display SAP test catalog,  hear you can also find what is new in EHP.

 

Step 5- Activate Business Function as below Screen

10.jpg

 

Example of Some important feature


A. GR/IR Report

 

  1.   List of Invoiced but Not Delivered Transactions

  2.  List of Delivered but Not Invoiced Transactions

 

B.  Open Item Age Analysis-

 

1.    Accounts Payable Age Analysis – Vendor Ageing     

2.   Accounts Receivable Age Analysis – Customer Ageing

 

  1. Time Dependent Attributes in FS00
  2. Stock on Posting Date
  3. Print out balance sheets and income statements periodically
  4. Authorization Check for Profit Centers
  5. Drilldown Reports for Profit Centers and Segments
  6. Assigning Tax Code Based on Region
  7. Foreign Currency Valuation History
  8. Reversal Reason in cancelation of billing documents in SD
  9. Depreciation Simulation Report
  10. Payment Terms Based On Shelf Life of Goods
  11. Down Payment and Down Payment Request linked to PO history
  12. Down Payment Clearing through Logistic invoice
  13. Payment Terms Based On Shelf Life of Goods
  14. G/L wise Inventory report (MB5B)
  15. Record down payment data at header and item level in purchase orders.
  16. Extended Document Flow in MM and SD Documents
  17. One-Step Stock Transfer for Subcontracting
  18. Replacement Materials for Customer Returns
  19. Internal table performance can be increased using secondary index which was not possible earlier.
  20. ABAP Editor adds new feature like code auto completion hence ABAP productivity can be increased.
  21. Crystal Reports integrated with ALV reports – ABAP list viewer can be a source for crystal reports.

And Much More

SAP NetWeaver Visual Composer Survey and News

$
0
0

Hi,

 

 

SAP NetWeaver Visual Composer UI5 Runtime is planned to be released with NetWeaver 731 SP11, in March 2014.

We will appreciate if you can fill this survey and give us some info about what do you think about VC.

 

2014-0040 SAP NetWeaver Visual Composer

 

Thanks,

 

Gad Ravid

 

VC Solution Expert

How to correct corrupted system variants?

$
0
0

Sometimes during a system copy/refresh you might face some problems with system variant corrupted.

Usually when you try to load them you get a dump. So here you will find options to correct these system variants.

 

1st  Option:   Use report RS_VARDOC or RS_VARDOC_610;
2nd Option:  Try to copy the system variants from productive system;
3rd  Option:  Delete the variant and create again.


Some background:

 

•Main variant table/field: 

 

Table  VARI - ABAP/4: Variant storage
Field CLUSTD (LRAW)- Contents of variant

 

•Functions usefull:

 

RS_VARIANT_CONTENTS
RS_CHANGE_CREATED_VARIANT


Sample report to mass change variants:


http://wiki.scn.sap.com/wiki/display/Snippets/Mass+Change+of+Variants?bc=true


Custom Button on IH08 Transaction Through BADI

$
0
0

In SAP Plant Maintenance, there might be a requirement to enable a custom button on IH08 transaction Output to perform some action. For example, say Print Equipment Labels from IH08.

 

I would explain how to Enable the Custom Button on IH08 Output Transaction which can be used for different purpose.

 

BADI : BADI_EAM_RIEQUI20_FCODE_CUS1

 

Image1.jpg

 

 

Here there are 2 Function codes, one for RIEQUI20 & one for RIEQUI21. Our Interest will be the function code +CUS1 on RIEQUI20.

 

Image2.jpg

Implement the above said BADI, provide BADI implementation name (ZXXXXXXXXXXX) and BADI implementing class (ZCL_XXXX_XXXXX)

 

Image3.jpg

This will implement the Interface Method IF_EX_BADI_EAM_LIST_FCODE~EXECUTE_FUNCTION_CODE.

 

Now Provide Function text, Any ICON(according to your Requirement, from INCLUDE <ICON>) and ICON text.

 

Image4.jpg

My Example, for ‘Equipment Print’

 

Image5.jpg

You have Enabled Custom Button now, Write code in the method IF_EX_BADI_EAM_LIST_FCODE~EXECUTE_FUNCTION_CODE of class ZCL_XXXX_XXXXX.

 

Image6.jpg

Automatic Dispute Case Correspondence

$
0
0

When customers take deductions from the amount they need to pay, we can create a dispute case in dispute management to analyze and settle the disputed amount.  If the dispute case information is sent to the customer in time we can expect the disputed amount at earliest. So the dispute case correspondence is very importance for the effective dispute case settlements

 

If the customers are not notified about the new dispute cases that are being created then the cash settlements will be delayed. If we automate the dispute case correspondence then the customers will be notified about the dispute cases in time and the settlement process will be speeded.

 

When we create dispute case in accounting we can enter the data of a contact person which becomes the correspondence recipient. This is then included in the dispute case as an attribute and used for customer correspondence. In Customizing, we can define that an automatic notification is to be created and sent to the customer. The communication channels such as e-mail, fax, or letter configured for the contact person is used is used for correspondence.  In Dispute Case Processing, the system can create and send correspondence automatically. This means that the user does not have to create the relevant correspondence and send it to the customers.

 

Example – when the dispute case 242 is created, automation of dispute case correspondence will generate the dispute case letter and send it to the business partner contact person as shown below


fig. 1.jpg


Email will be triggered and sent to the contact person as soon as the dispute case is created

fig. 2.jpg

 

Dispute case letter as attached in the email

fig. 3.jpg

When we are processing dispute cases, we may need to contact a contact person at the business partner. Here in correspondence, the contact person is the correspondence recipient.

 

We can also use the contact person defined in Accounting for a customer. In addition to the contact person data stored in customer master, we also store a key (FIN_CONTACT_KEY) as an attribute to the dispute case. Using this contact person key, the system can access the contact person data in Accounting during the creation of correspondence. If we change the contact person data locally in the dispute case, this key is deleted. In this case, the changed attribute values of the contact person fields from the dispute case are used to create correspondence.

 

The user recognizes whether the contact person key exists, and therefore the contact person data in the dispute case and in Accounting agree, from whether or not the contact person fields in the dispute case are modifiable:

 

- Contact person key exists: Fields not ready for input, data synchronized with FI-AR

- Contact person key does not exist: Fields ready for input, data changed locally in the dispute case

 

If the contact person key exists, the communication channel (e-mail, fax, letter) defined in FI-AR is used in the creation of correspondence. For letters (communication type LET), the following order applies:

 

     1. Business address of contact person is used, provided one exists

     2. Customer’s address is used, with the suffix “For the attention of <Title and name of contact person>”.

 

If the contact person key does not exist, the current attribute values of the contact person fields (FIN_CONTACT*) in the dispute case are used. The following order applies for the communication channel:

 

     1. e-mail

     2. Fax: The fax number and the country of the fax number of the fax address must exist

     3. Letter: If both addresses are unknown or incomplete, a letter is created and sent to the customer’s address.

 

The correspondence is created in the language of the contact partner address.

 

The technical basis for this automatic correspondence is the Post Processing Framework (PPF). With this component, we can have follow-on activities (actions), such as the creation of correspondence, triggered and processed automatically based on conditions. We can define and configure these actions in accordance with client requirements. These actions are grouped in an action profile which is assigned to a case type. For successful automation of dispute case correspondence we should ensure that all the configuration settings are done properly as shown below


fig. 4.jpg

fig. 5.jpg

 

The PPF receives the required data like key of the dispute case, correspondence recipient, and further technical information, such as the action profile and the context of the application and creates the correspondence (action). To do this, it evaluates the scheduling and start conditions, assigns the partner (correspondence recipient) to the action via the partner function used, and manages the actions to be scheduled. Actions that are configured such that they do not have Processing via Selection Report as processing event are executed when the start conditions are fulfilled.

fig. 6.jpg

In the standard Configuration, the following action definitions are already defined for automatic correspondence:

fig. 7.jpg


Dispute case created -

Correspondence for creating a dispute case: This is configured in Customizing such that it is always scheduled when the attribute Business Partner (FIN_KUNNR or FICA_GPART) is set. The Action Summarization is configured such that only one such initial correspondence is created.

fig. 8.jpg

  fig. 9.jpg

Dispute case was closed -

Correspondence for closing a dispute case: This is configured such that it is created when the status Closed is reached.


fig. 11.jpg

fig. 12.jpg

Dispute case was escalated -

When we set or change an escalation reason, an e-mail is sent to the coordinator of the dispute case automatically.

To enable this, we have to define an e-mail address in the user master record of the coordinator.

fig. 13.jpg

fig. 14.jpg

Finally Action Profile need to be assgined to the Case Type

fig. 10.jpg


How to configure Electronic Bank Statements in SAP

$
0
0

Introduction

 

Medium to large scale businesses do thousands of transactions each day. Lot of these transactions are banking related. Reconciling bank balances with book balances manually is not possible.

 

Uploading manual bank statement in ERP system is a time consuming affair and prone to clerical errors due to manual intervention. Treasury staff in an organisation may end up spending lot of time usually at the end of month for reconciliation.

 

Electronic bank statement feature provided by SAP can save a lot of time and is error free. SAP will upload the file which is sent (FTP) by bank. Based upon SAP configurations financial postings will be done. This configuration will upload the statement automatically and at the same time will do the bank sub ledger postings and clearing postings.

 

Prerequisites

 

Following are the basic requirements for setting up EBS in SAP:

 

  • House Bank
  • Bank file in specified format
  • SAP Configurations for EBS
  • Set up connection between SAP and bank for file transfer mostly secured (sFTP)
  • SAP automated batch set up

 

SAP Configuration of electronic bank statement(EBS)

 

Financial Accounting --> Bank Accounting --> Business Transaction --> Payment Transactions --> Electronic bank statement

 

EBS is done at Chart of Account Level

 

1. Account symbol creation - Account symbols are specifications for general ledger accounts. These are posted with each possible transaction contained in bank statement.

 

2. Assign accounts to account symbol - GL accounts are mapped to account symbols in this step.

 

3. Create keys for posting rule - Description for the necessary posting rules is entered in this step. Each posting rule represents a business transaction.

 

4. Define posting rules - In this activity posting specifications for each posting rule is created. You specify how a certain business transaction is to be posted with which posting key, document type and posting type.

 

5. Create transaction type - Transaction type contains the external transaction type. External transaction types are codes used by banks to specify the business transaction in bank file. Transaction types in turn  are link between External Transaction Types, Posting Rules and Interpretation Algorithms. Interpretation algorithm interprets the note to payee line in bank statement and accordingly clears the open items accordingly.

 

6. Assign bank account to transaction types - Last step involved is assigning bank accounts with transaction types as defined above. This step contains the list of external transaction which are valid for a house bank. Please note that assignment is of Bank account number and Bank Routing Number and not of GL account in this step.

 

Summary Relationship


GL Account --> Account Symbol --> Posting Rule --> Transaction Type (linked with bank account number and algorithm) --> External Transaction Codes

 

File format


There are many EBS file format currently being used. Most commonly used are BAI, MT940 and Multi Cash formats.

BAI format is a standard format and recommended by SAP. Main difference between BAI and other formats is that it allows file to be processed even if some of the external transaction codes are not available in SAP. System will post all those transactions which have valid external transaction codes. Missing codes need to be mapped and the statement need to be reprocessed using standard SAP transaction code FEBAN (Edit bank statement).

 

Illustration

 

Company X has decided to use SAP delivered Electronic Bank Statement processing for uploading and reconciling its daily bank statement. You have been asked to configure EBS upon considering below details:

 

  • Company received listing of external transaction codes (BAI codes) used by bank
  • External transaction code 100 signifies Agency fees
  • External transaction code 101 signifies interest earned
  • Bank account number is 1122334455 and routing number is 2778899 of the house bank

 

Configuration steps

 

  • Define the account symbol for

       -  Agency Fees as AGENCY

       -  Interest Earned as INTEREST

       -  House bank as HOUSEBK1

 

  • Link the account symbols with corresponding GL accounts

 

  • Create posting key for

- Agency Fees as ZAGY

- Interest Earned as ZINE

 

  • Define the posting rule for

- Agency Fees (ZAGY) with posting key 40 assigned with account symbol AGENCY and posting key 50 assigned with account symbol for House           bank  HOUSEBK1

- Interest Earned (ZINE) with posting key 40 assigned with account symbol INTEREST and positng key 50 assigned with account symbol for House        bank HOUSEBK1

 

  • Create a transaction type as TRAN1

 

  • Assign transaction type

        - 100 with  posting rule ZAGY along with Interpretation Algorithm as 12

        - 101 with posting rule ZINT along with Interpretation Algorithm as 12

 

  • Assign bank account number and routing number with transaction type TRAN1

Methods to find Customer/User Exit's & BADi's for a Transaction Code!

$
0
0

Dear Friends,


This blog is going to explain you many ways to find the User Exit's & BADi's for desired transaction code. Since the objective of the document is to explain the search method I'm not going to take much time in explaining the functionality of the said features.


In order to explain you in the simple manor I've taken 'MM01 - Creation of Material Master' transaction code as an example. Please follow the below steps to know the different ways of finding user exits and BADi's.

 

Method 1:

    • Enter the transaction code in the command bar, for which you would like to search for an user exit and then click on enter, so that it would take you to the initial screen of the transaction.
    • Go to Menu bar - Click on 'System' and then click on 'Status' as shown in the below screen shot.

            1.PNG

      • Once you click on the 'Status' below screen would get popped up. Here, double click on the program name.

            2.png

      • Once the program window is open, go to Menu Bar --> click on 'Goto' and then click on 'Object Directory Entry'.
      • The above step would take you to a pop up window and here copy the Package Name as shown in the below screen shot.

              3.PNG

      • Once you get the package number execute the transaction code SE80 (We can also try with SE84) and then click on 'Repository Information System'.
      • As soon as you done with the above step the system would display the respective Objects list, here drill down Enhancements and then Customer Exists.
      • Now, double click on Enhancements, which is under Customer Exists, so that the selections screen would get displayed in right side.
      • Here go to package field and paste the copied package number from the previous step (program) and then execute the transaction as shown in the below screen shot.

            4.PNG

      • As soon as you execute the above step, it would display the list of user exits for the relevant transaction / package number.

             5.PNG


    In order to find out the relevant BADi for a transaction code, follow the above steps but instead of expanding Customer exits, expand Business Add-ins as shown below.

      • Drill down Business Add-ins and then double click on Definitions, so that the selection window would get open in the right side of the screen. Here enter the copied package number in the Package field and then execute the transaction as show below.

    11.PNG

      • As soon as you execute the above step, it would display the list of BADi's for the relevant transaction / package number.

    12.png



    Method 2:

     

      • Execute the transaction code SE93 --> enter the desired transaction code in Transaction Code field and then click on Display button as shown in the below screen shot.

    6.PNG

      • Once you click on Display button it would show the below screen, double click on the program name.

    7.png

      • Once the above step is done, go to Menu Bar--> click on 'Goto' and then click on 'Object Directory Entry'.
      • As soon as you done with the above step, the system would pop up with a window as shown below, copy the Package name for the further process.

    8.PNG

      • Once you get the package number execute the transaction code SMOD --> place cursor on Enhancement field and then press F4.
      • It would take you to the below screen (Repository Info Systems). Enter the package number, which has copied from the previous step. And then click on enter button.

    9.PNG

      • As soon as you execute the above step, it would display the list of user exits for the relevant transaction / package number.

    10.png


    Method 3:

    Along with above methods I would like to show the ways to find the Exist / BADi's at configuration / SPRO as well.

    Example: If you would like to know the relevant user exits at the functionality level like, ‘Logistics Invoice Verification’, follow the below steps.


      • Execute the transaction code SPRO and click on SAP Reference IMG --> drill down Materials Management --> Logistics Invoice Verification --> Maintain Customer Exits and Business Add-Ins --> click on IMG Activity Document on Maintain Customer Exits for Invoice Verification, so that it would show the list of Customer / User Exits for the functionality.

    13.png

    14.png


    In order to find out the relevant BADi at the functionality level, follow the above steps but instead of clicking on click on IMG Activity Document for Maintain Customer Exits for Invoice Verification, click on IMG Activity Document for Maintain Business Add-Ins for Invoice Verification, so that it would display the , so that it would show the list of BADi's for the functionality.


    15.png


     

    Method 4:

    If you find difficulty in finding the exact node, follow the below steps


      • Execute the transaction code SPRO and click on SAP Reference IMG--> click on Find button or press Ctrl+F.
      • Once you click on find button the below pop up window gets displayed --> enter Customer Exits in the Search Term field and then press enter button.

    16.PNG

      • Once you hit enter, the system would provide you the list of results for the search term, which you have entered. You should be very patience in finding the right node as the list would be very big. You can take the 'In Area' reference as that would provide the information about the functionality of the node. Refer the below screen shot for your info.

    17.png

      • As soon as you find the right node, double click on it and it would take you to the configuration node, for which it belongs to.

    18.png

    • Now you can click on IMG Activity Document for Maintain Customer Exits for Invoice Verification to display the relevant Exits.


    Note: 1. Since I've already displayed the screen shot for the above step, not displaying the same for the 2nd time.

       2. Follow the same steps to get relevant BADi's.


    Hope the document might find you useful. Thanks for reading the document and I would welcome your comments for improving the document quality.


    Thanks & Regards,

    Narayana N

    Tcode SNOTE -> Step by Step guide

    $
    0
    0
    Applies to

     

    SAP 3.x and 7.x

     

    Summary

     

    This document will serve as a step by step guide for downloading OSS notes using the Tcode SNOTE.

     

      Author: Pallavi Alat

     

      Company : Accenture Services Pvt. Ltd.

     

      Date : 15 May 2014

     

     

    Author Bio

     

    Pallavi Alat is working in Accenture and has expertise in SAP BI.

     

     

    Introduction

     

    The Tcode SNOTE is used to download OSS notes directly to the application server from SAP Marketplace.

     

    Below is a step by step guide of how to work with the Tcode :

     

    Steps

     

    1. Once you goto the Tcode SNOTE, the note assistant window will open. It will list the Existing notes hierarchy.

    1.PNG

    2. Expand the hierarchies and Click on the find button.

    2.PNG

    3. Enter the note number that you want to find. Choose the search ‘in whole hierarchy’ -> Find

    3.PNG

    4. If found, then it will be highlighted as shown below.

    4.PNG

    5. Double click on the note and it will be displayed as below.

    5.PNG

    6. If the note does not exist, on clicking the find button, you will get the below message.

    6.PNG

    7. In such cases you need to download.  Navigate as shown below :

    7.PNG

    8. The below screen will open up

    8.PNG

    9. If there is only one Note to be downloaded, then you can directly enter the number in the text box. If you want to download more than one notes together, click on the yellow button at the right. Enter all the sap notes number and Execute. Click on Execute once again.

    9.PNG

    10. The following message should be displayed for each of the notes. Once downloaded, you can view them as described in steps 2 to 4.

    10.PNG

    11. If you enter a wrong note number, the below message will be displayed

    11.PNG

     

     

    Plant Divestiture – Case Study

    $
    0
    0

    Business Context:

     

    As we recently embarked upon a client demerger requirement mandating a plant divestiture scenario, this case study has been prepared to share some of the key learnings on the same. This work majorly covers the questionnaire for understanding scope of work under various modules Viz. FI, CO, PP, QM, PM, MM & SD.

     

    The below flow depicts the business context:

     

    Depiction.JPG

    As shown above (Note: all nomenclature changed intentionally to retain client-confidentiality), under the target system, one of the plants i.e. PLN1 under company code TES1 shall be moved to a new company code set-up with a new sales organization aligned. Also, a new replica company code shall be created for TES2 with both the assigned plants PLNA and PLNB also recreated with existing sales set-up too reproduced.

     

    Module-Based Questionnaire

     

    FI

     

    a.       a. Global settings & General Ledger:

     

    1.       1. Can the existing Chart of Accounts (GL accounts) and other financial global settings including fiscal year variant, posting period variant etc., be extended to new company code(s) proposed?

    2.       2. Any mandate to have alternative chart of accounts for new company codes’ localization requirement?

    3.       3. Can existing tax procedure / tax codes be used in their current for the new company code(s)?

    4.       4. To be mapped: New company code – name and address, Company code registration details like VAT etc., Company linkage with company code, its name and address (needed mainly for trading partner)

     

    a.      b. Accounts Payable:

     

    1.       1. List of the existing vendors (third party, inter-company and employee) which are required to be extended to new company code

    2.       2. Can existing Payment procedure & its interface (if any) be extended to this new company code?

     

    b.      c. Accounts Receivable:

     

    1.       1. Similar to Accounts payable above (details required for Customers)

    2.       2. Can all the existing functionalities in AR (including interfaces) in old company code be extended to new company code or exclusions if any? Ex: Credit control area,  Dunning, HO-Branch combination etc.

     

    c.       d. Bank accounting:

     

    1.       1. Details of the list of bank accounts to be created in new company code?

    2.       2. Can the existing set-up in terms of Check deposit, Electronic bank statement and lockbox (if any) be extended to new company code?

     

    d.      e. Asset accounting:

     

    1.       1. Local depreciation / parallel depreciation area if any, required in new company code?

    2.       2. Can the existing Chart of Depreciation be extended to this new company code?

     

    CO

     

    a.       a. General Settings: Can the new company code be assigned to existing Controlling area?

    b.       b. Cost center accounting: List of new cost centers that are to be created in new company code?

    c.       c. Profit center accounting: List of profit centers that need to be newly created / already existing ones to be extended to the new company code

    d.       d. Internal orders: List of new internal orders to be created

     

    a.       e. Product Costing:

     

       1. If standard costing process is followed in the current set-up – how the same needs to be set-up in new plant / company code combination – i.e., existing material standard price in current plant / material number to be copied to new plant (and / or material number)?

       2. Approximate list of open Production orders / Service orders / Sales orders etc., to be migrated to new Plant during cutover – this will aid in assessing progress on these objects from CO point of view.

     

    b.      f. Profitability analysis (COPA): Any new operating concern, new value fields to be created / derivation strategy to be adopted for new company code or existing functionality in COPA be fully extended to new company code?

     

    c.       g. Customized reports / forms and other RICEFs:

     

      1. List of customized RICEFW’s to be extended to new company code / new plant (needs to be done through security authorization).

      2. Details of customized RICEF’s where address should be changed to new company code / new plant. (to be checked through current SO10 text)

     

    PP

     

    1.      1. Master data details - Material Master, BOM, Routing, Production version etc. need to be migrated to new Plant?

    2.      2.  Naming conventions for Material Masters? (does this need any change)

    3.      3. Naming conventions for Work Centers? (does this need any change)

    4.      4. Do we have production versions? If yes, naming conventions for Production Versions?

    5.      5. List of MRP controllers & naming conventions for the MRP Controller?

    6.      6. List of production scheduler & naming conventions for the production scheduler?

    7.      7. List all work center responsible & naming conventions for the same?

    8.      8. What MRP types are used? Is there any special configuration required at Plant level

    9.      9. Are there any custom MRP types created in system? For what business reason?

    10.  10. Do we have any MRP areas defined? Business purpose for the same?

    11.  11.What planning strategies will be used?

    12.  12. Production Process – Discrete/repetitive manufacturing.

    13.  13. Any custom order types defined? Any rework order types defined?

    14.  14. How is the cost settlement done for Production and rework orders

    15.  15. List any custom reports used in Planning and production process that need to be migrated to new plant (target system)

     

    QM

     

    1.     1. Is QM activation required for the Plant? (relevance)

    2.     2. Have we defined laboratory as a work center?

    3.     3. Material Specifications used for Quality Inspection or Inspection Plan?

    4.     4. Details of material/material group/product group using Material specifications.

    5.     5. Is the business using ‘classify’ the master inspection characteristics?

    6.     6. Is transfer of quality inspection data to batch management used?

    7.     7. Details of current catalogs and their structure?

    8.     8. Are there any special sampling schemes to calculate sample sizes?

    9.     9. How the inspection lots for goods receipts is created?  (Implying Manually/Automatically based on MM-QM view setting)

    10.  10.Does the business records results for inspection points during production process? 

    11.  11.Which type of interval (time-related/quantity-related/freely defined) does the business use for performing inspections?

    12.  12.Are notifications used? Key criteria used to differentiate notifications? Details of different notification types?

    13.  13.Is the creation and activation of QM order based on the notification? Where are the costs to be settled?

    14.  14.Do we have quality inspections for deliveries to customers?  Elucidate the procedures used.

    15.  15.What information is populated in quality certificates? Do they contain information about the finished product alone or data about components from the production chain as well?

     

    PM

     

    1.      1. Is the business using cross plant Maintenance planning?  

    2.      2. How the hierarchy of functional locational structured?

    3.      3.What equipment categories have been defined in the existing system?

    4.      4.How are equipment BOM Structured?

    5.      5. Number range for Equipment (External or Internal?)

    6.      6. What task list types are in use in the system?

    7.      7. What notification types have been defined in the system? Any custom notification types?

    8.      8. Do we have standardized codes in the existing system? If yes, which code categories are needed to be implemented?

    9.      9. What user statuses have been created in the system and how are they behaving?

    10.  10. How time confirmation for external service is done in the current system?

    11.  11. What measurement points and counters are defined in the present system?

    12.  12. How the maintenance plans are created in the system (Individual/group of Maint. items)

    13.  13. Is calibration Process using plant maintenance orders used?

    14.  14. What are the order types used - Preventive, Breakdown, refurbishment etc.? Also, list any special order types used

    15.  15. Do we have inventory for the Plant Maintenance related items? Is yes, how these are consumed during the process?

    16.  16. Any custom reports or developments – Details?

     

    MM

     

    1.      1. Details on the new Organization Structure?

    a.       Number of Plants

    b.      Number of Storage Locations

    c.       Number of Purchase organizations

    2.      2. Expected volume of materials for the new plant?

    3.      3. Expected volume of vendors required in new company code. Are Plant wise vendors required?

    4.      4. Is there any customized Purchase order document type(s) required for the new plant?

    5.      5. How many pricing procedures required? Do they exist in the current system or to be designed new?

    6.      6. Is Release Strategy required? If so, which are all the documents requires release strategy?(PR, PO and Contract – For example)

    7.      7. Can existing release strategies be modified or new release setup required for new company code /plant?

    8.      8. Are release Workflow and Mobile applications required for release?

    9.      9. Any new business process(s) required in the new company code / Plant?

    10.  10.Split valuation required for the new plant?

    11.  11. Does workflow exists in Invoicing for the new company code?

    12.  12. How many Forms/ Outputs required for the new plant and list of the same?

    13.  13. Any Customized reports required for the new plant? If yes, details

    14.  14. Any existing customized report needs to be modified/redesigned with respect to the new plant?

    15.  15. How many users for the new company code / Plant? (post divestiture)

    16.  16. Expected volume of open Transaction data for the new plant? (see below)

    a.       Open Purchase orders / Goods receipts / Invoices

    b.      Initial Stock

    17.  17. Any Interface requirement exists for the new company code / Plant?

    18.  18. If the plant is removed from the current company code and assigned to new company code, what are all the activities required in the old company code? (existing set-up)

     

    SD

     

    1.      1. How many new sales Organizations are required? Address details for new Sales Organizations?

    2.      2. Which distribution channels/divisions to be assigned to new sales organizations?

    3.      3. Details of Sales Offices, Sales Districts and Sales Groups? (And other auxiliary sales related inputs)

    4.      4. Details of new Shipping points/Routes?

    5.      5. Sales document types to be assigned for new sales areas?

    6.      6. Pricing Procedure determination details for new sales areas proposed?

    7.      7. Intercompany configurations required for new sales area? (Plant to sales area, customer etc.)

    8.      8. List of Customer masters to be extended to new Company Code/Sales areas? If old Company Code is to be scrapped, customers to be set 'deletion flag' at old Company Code?

    9.      9. List of Material masters for which sales views to be extended for new sales organizations/distribution channels?

    10.  10. List of CMIRs to be created for new Sales Organizations?

    11.  11. List of sales processes for new plant? (Normal sales, Interco-Sales, STO, Free Samples etc.)Any new sales process to be configured for new plant?

    12.  12. Open Sales Documents in old Company Code - will they be set 'Reason for Rejection' or be processed completely before going for the new set-up?

    13.  13. Customized reports based on Sales Org/Plant/Company Code to be enhanced for new set-up?

    14.  14. List of output types to be used for new plant? (Sales, Shipping, Billing etc.)

     

    Summary:

     

    Though may not be exhaustive, the questions above, covering some of the core SAP modules will surely help practicing consultants in understanding the quantum of work that may be involved in a potential business demerger requirement.

    How Virtual Sales is Assisting Enterprise Sales or Traditional Field Sales

    $
    0
    0

    Virtual sales is another word for Inside sales which originally came in the late 1980’s in Britain as a process to do telemarketing rather going with complex B2B or B2C Sales processes. It can also be termed as ‘Remote Sales’.

     

    The inside sales process is used to run the sales campaign working from the office using telephone , email or web based systems.

    This model is often cost effective because:

     

    1. Unlike traditional salespeople going for face-to-face client meeting, by sitting inside the office an inside sale rep can develop first level lead by briefing their product/s or service/s to prospect.
    2. Using Inside sales model within a day a sales rep can reach to multiple prospects spread across a geography e.g. a web based CRM tool can be used to send 100’s of email in a single point of time and simultaneously lead status can be tracked.
    3. The qualified leads can be passed by inside sales rep to business development managers to close the deal.
    4. Has replaced almost the door to door sales concept

     

    *As per the HBR blog review, many companies are ramping up their Inside sales team and investment, like-

     

    1. Astra Zeneca has replaced virtually all of its field sales force support for its mature brand Nexium with a 300-person inside sales team. The team provides for most doctors’ basic needs for samples and information at a substantially reduced cost.
    2. IBM has invested in social media training, toolkits and personalized digital pages to help its inside salespeople generate leads and manage account relationships. Early results include a 55% increase in Twitter followers and a significant increase in the number of high-quality inbound leads.
    3. SAP has refocused its large and growing inside sales team towards working with channel partners, rather than directly with customers, as part of a strategic initiative aimed at increasing channel sales to 40% of the company’s total sales by 2015.

    (*Source: http://blogs.hbr.org/2013/07/the-growing-power-of-inside-sa/)

     

    There are companies (X) who wants to outsource their sales activities only to focus on their core working areas. The companies (Y) offering inside sales and lead management services comes here in picture who offer them to grow their business, free up engaged resources thereby reducing operating cost etc.

     

    Figure : The Inside Sales process workflow:

    InsideSales WorkFlow.jpg

    Above is the pictorial representation of a lead management and inside sales process. The process steps are:

     

    1. Company X is an outsourcing company – It runs campaign to find the type of industry/geography etc. that would buy their products or services.
    2. Company Y will gather the requirements from company X and instruct their database development team to generate the data.
    3. Once the database is created, the team uploads the data in the web based CRM tool.
    4. The Inside sales team prepares the artifacts like email scripts, calling scripts which would contain the company X product/services offerings and capabilities.
    5. The Company X representatives will verify these artifacts and then the Salespeople will be aligned with the inside sales people.
    6. Prospecting Phase: Now the role of inside salespeople starts here, using CRM tool / telephone they can start sending artifacts to the prospects. They perform the following activities:-

     

                     a)      Personalizing the email or telephone talk as per the prospect’s requirement

    b)      Sending artifacts about the company X details

    c)       Calling and explaining the prospect about the Company X product or service offerings

    d)      Identifying the need / pain areas of the prospects

    e)      Qualifying the lead as Cold/Warm/Hot

    f)       Setting up 1st level of meeting with the Company X – Sales people

     

    7.    Finally, in the review meeting with company X sales representatives, the leads are verified and passed for the next level of discussion.

    8.    Revenue realization by the Company Y from the Company X on the qualified leads.

     

    Now a days the inside sales is no longer a telemarketing process and cannot be considered just as a customer service approach. In the recent years paradigm shift has been observed and the sales pitch target has moved from small business like (B2C) to big B2B and high-end B2C businesses. With newer technology in place like WebEx and video conferencing, the insides sales is definitely going to vouch for the frontline sales and making the entire sales process efficient and cost effective.

     

    References:

    Viewing all 131 articles
    Browse latest View live


    Latest Images

    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>