In SAP Standard it is possible to Cancel the Invoice for which we have already created & completed Returns Order. Similarly we can create Returns Order for an Invoice that is already Canceled.

We felt that is not logical behavior & raised a query to SAP & below is the reply we received:

Quote

Your system works correct, there is no program error.

Creation of a sales documents with reference to a billing document does not prevent any actions done on the billing document.

Furthermore it is also possible to create a return with reference to a canceled billing document.

In transaction VOFA you could set an own copying requirement (field TVFK-GRBED_S) for the used billing document type.

Unquote

So we decided to develop Custom Routines & insert the same at appropriate places. (Routines were created / modified after taken necessary access keys from SAP)

1. Sales Invoice for with Returns Order have be created, should not be allowed to be canceled.

Following was the Routine created:

FORM BEDINGUNG_PRUEFEN_601.

* This Routine is used to restrict cancellation of billing documents against Return Orders.

*{ INSERT ECDK951721 1

DATA : lv_vbeln TYPE vbeln_von.

SY-SUBRC = 0.

IF vbak-vbeln NE space.

SELECT SINGLE vbeln FROM vbfa Into lv_vbeln WHERE vbelv = vbak-vbeln AND

vbtyp_n = 'H'.

IF SY-SUBRC = 4.

SY-SUBRC = 0.

EXIT.

ELSEIF sy-subrc = 0.

MESSAGE 'Billing document cannot be canceled as Returns Order was generated against this Invoice' TYPE 'E'.

ENDIF.

endif.

*} INSERT

ENDFORM.

The above Routine was assigned at Copying Requirements for Cancellation in Billing Type

Now when we tried to Cancel the Invoice for which Returns Order was created, system gave a error message.

2. Now, for Invoices that are already Canceled, system should not allow to create Returns Order

Here we have to create / modify a Copying Requirement & assign the same at Billing Document to Sales Document Copying Control (T-Code VTAF)

Normally Copying Requirement 021 is assigned at Billing Document to Sales Document Copying Control so the below code was added to the 021 Requirement & new Requirements (601) was created).

Following was the ABAP code added to standard Routine 021 (& new Routine created):

IF vbrk-fksto = 'X'.

MESSAGE 'Return Order Cannot be Raised Against Canceled Billing Document' TYPE 'E'.

ENDIF.

After assignment of above new Requirements to VTAF Copying Controls, when we try to create Returns Order for Canceled Invoice, system gave a error message.

I am trying to upload images of the above settings, but there seems to be some issue currently.

Business Requirement:

In some companies client attaches documents/approvals in any transactional or master data. Any user who have its display or change access can delete or edit this attachment. We can restrict users from deleting or editing attachments in all documents. Please check below process for this.

Run T-Code SU21 and create authorization object with display activity 03 only.

Create object class. If you want to use any existing class please leave this step.

Enter class name and text.

Now create authorization object.

Create only one activity 03 for display.

Run T-Code SE24

Enter class CL_GOS_SRV_ATTACHMENT_LIST into object type.

Copy standard class into your own Z class and click on green tick/enter. Give you package name and save it in new transport request.

In the below screen double click on check_status.

Add authorization check. Coding is

AUTHORITY-CHECK OBJECT 'ZATTACH' ID 'ACTVT' FIELD '03'.

IF sy-subrc = 0.
on_mode_changed( 'D' ). "--- For display
ENDIF.

Logic is that field 03 is for display in authorization object activities. ‘D’ is an indicator for display mode. You have to assign this object only to those users to whom you want to restrict for editing and deleting attachments. The users without this object can still delete and edit attachments.

Add Zclass in T-Code SGOS

Select VIEW_ATTA in Name of Service. Status Gen. Service should be active and enter Zclass name in class F.GEN.Service field.

Assign authorization object to user and give activity 03. Now test in any attachment list. Edit and delete buttons will be in display mode as you can see in below screen.

Following is the screen shot for the user who has full access and I have not assigned authorization object to this user. So this user can change and edit attachments.

Try this in your system and don't forget to rate and comment if you find this a helping document.

Thanks

Moazzam Ali

Business Requirement:

Sometime client asks for hiding some specific condition value like VPRS etc from condition tab of sale order or invoice. This is not possible in standard. Also sometime a requirement comes that only specific users can enter manual discount condition in Sale order. Most of the people give V_KONH_VKS authorization object as a solution. But this is not for entering condition in sale order. This object works in VK11, VK12 and VK13. For hiding or entering manual condition there is an SAP note 105621. All process has been described step by step in this note. I am just explaining it with screen shots because I have seen many guys who know this note but still don't able to implement this.

Create Authorization Field

Run TCode SU20 and click on create button

Create two authorization fields with following inputs

Enter your package

Create new transport request

Create Authorization Object

Run Tcode SU21 and Click on this icon and select Authorization Object

Enter object name, text, class and field names. Field ACTVT is not necessary. I have added in screenshot but you can create without this field too. It works fine without this field. Only add two fields ZKALSM and ZSTUNR.

Create message

Run TCode SE91 and Enter message class VH and number 609 and click on Change

Select this option

On message number 609 enter your text which will be shown as error message when user will enter condition which he is not allowed to enter.

Create Includes

Run TCode 38 Enter include name ZZAUTH01, select Source code option and click on create button and enter the following values

Here you can enter coding provided in SAP note 105621.

Reproduced text removed by G. Lakshmipathi & Jyoti Prakash

Now give your package name and save this. Create another include by following the same procedure and give title of this include as "Authorization check for creating condition". Coding for this 2nd include is

Now you need to add these includes in program LV69AFZZ. Here you have to take help of your ABAPER for implementing this Enhancement. Once its implemented, you can add your coding in it. I am not adding screens of how to implement enhancement but I am attaching screens of implemented enhancement here. Go to T-Code SE38 give program LV69AFZZ and click on display button.

Result:

Give authorization and test this. I have given authorization of pricing procedure ZM0001 steps 190-290 to my test user. System will allow to display and enter only those conditions which comes in between these step numbers. For all other steps and conditions system will not show condition value and if any condition is manual user can not enter this condition. Check below authorization and pricing procedure.

A user having full access of these pricing procedure will have following screen.

A user having limited access like I said step numbers 190 to 290 will have following display screen.

If user try to enter condition which he is not allowed system will give error. In below screen I am trying to add ZCOM condition which is manual but system didn't allowed me. This can be controlled at user level.

If you see the SAP note 105621 there are some other settings too regarding creating authorization profiles. I have not mentioned those settings here because these are not mandatory. If you want to create an authorization profile having full access of all pricing procedures and all steps you can create with SU03 and SU02. Take help of your BASIS guy if required. Assign this profile to users you want to allow full access and for all other users you have to give them relevant pricing procedures and step numbers in pricing pricing procedures. 

Please give your remarks if this is helpful for you

PROCESS

Sales transactions are the most omnipresent transactions happening everywhere at any point of time earning revenue for the organisation. To streamline and prevent the undesirable chain of intractable transactions they need to be aligned in proper sequence with judicial controls. One such tool which helps to achieve this objective is the statuses used in the sales transaction at header or item levels.

Order header and item statuses I refer here differ from the normal completion status we are used to. These statuses are classified into system status and user status. While the system status automatically controls the sequence of transactions and comes packaged in SAP, the user statuses are customizable to the business requirement. These statuses are sequenced and tagged to either the execution or prevention of various transactions. This bunch of controls is encapsulated inside a status profile. Finally the status profile is linked either to the document type or item category. 

Though it is efficient and effective to manage the process through status profiles, it is not possible to extract reports based on the status of the sales orders or their items. This is due to lack of knowledge on the database tables behind the process and also limited usage of this functionality in a stand alone sales scenario.

This document tries to break this myth and helps to create a simple quick view query to know the status of sales orders or to find the orders of a specific status.

TECHNICAL INFORMATION

The repository of information related to statuses is controlled mainly by the field object number which is updated in every transaction in each possible level. For example this field called object number is available in VBAK for the sales order header and VBAP for the items of the sales order. The field OBJNR in VBAK and VBAP is the key field used to further mine the details of the user and system status.

If the sales order header or item or both are enabled with a status profile, then the VBAK-OBJNR and VBAP-OBJNR will be updated with an automatically generated object number. The value of this field will be used in all further searches to get the desired status of the orders.

The next important table is the table JEST. This table also contains the field OBJNR and thus links either VBAK or VBAP with JEST. For the given object number, the table JEST will give the present user status and system status.  The status codes are presented in the field JEST-STAT. The user statuses always start with E and the system status starts with I. The status codes used in this table will need to be used to further extract the correct status as the user sees. The status codes shown in JEST are only the technical names of the statuses created.

There is also another table called JCDS which also contains the field OBJNR and this table will give the list of status changes the document had gone through. It should be remembered that it is easy to approach this table instead of CDHDR or CDPOS for any status related change documents.

The table JEST has the system and the user status of the document in technical terms. To know the correct description for them, two different tables should be used.

If the user status and its description need to be found out, the table TJ30T should be made use of. This table has got the status profile and the status codes. The status profile is indicated in the field TJ30T-STSMA and the status code is represented by the field TJ30T-ESTAT. As the combination of status profile and the status code are unique keys, both the values need to be provided to get the actual status.  As we already know, the status profile is either configured in the sales document type in table TVAK or at the item category level in the table TVAP.  By giving the status profile in the field TJ30T-STSMA and the status in TJ30T-ESTAT the field TJ30T- TXT04 represents the correct user status and TJ30T- TXT30 indicates the description of the status.

If the system status has to be found out, the status codes from JEST-STAT starting with I should be provided as an input in the table TJ02T- ISTAT along with the language key as EN for example in the field SPRAS. The resultant TJ02T- TXT04 and TJ02T- TXT30 gives the status and its description respectively.

Issue

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

Quite often, program variants are protected to avoid any unauthorised users from changing them.

For example, if this variant is for a program which is part of a batch plan, you don’t want to this variant to be modified as
it will disturb your automatic processes.

So you protect your variants. But a protected variant can only been changed by the
user who has protected this variant. The issue could arise when the original user has left the company or the variant is required to be changed for an urgent issue?

The solution

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

Go to transaction SE38, execute program RSVARENT, “Cancel Variant Protection” enter the program and the variant you want to
unprotect and execute. The program variant is now available for any changes.

Thanks.

How to Play with SPRO:

I think for the Beginners, this would be help for his Career a lot why because So many People doesn’t know how to play within SPRO especially above Tool Bar Tabs.

1. Actually, when you are going to create any activity in SPRO Level, you don’t know which Activity is Client Specific or Non Specific or Cross Client.

For getting above info please go by path as below,

SPRO->SAP Reference IMG Activity->Additional Information->Technical Data->Client Dependence

Click on Button “ Expand All “ (F6).You will get Screen shot like below.

2. In some case ,we didn’t get Transport Request when we are even customizing  any field in SPRO Level  ,in that time we are getting so much confusion as this have TR or not . If incase it wants to move in DJX to QJX  then we are falling so much trouble .For this ,SPRO is very & very helpful when we know ,how to use this .We can get as any customization level as it is having Automatic TR ,No TR or Manual TR info .

For getting above info please go by path as below,

SPRO->SAP Reference IMG Activity->Additional Information->Technical Data->Transport Type ( You can data like below picture ).

3.If any another module Consultant or User may come and ask as this Field is  Mandatory Activity ,Optional  Activity or Non Optional Activity in Project Level ( like Mandatory ,Optional and Required ) then we might be take some time to say as this is so and so ( In this case ,even some people doesn’t know ,how to get correct data in SPRO level ) .

For getting above info please go by path as below,

SPRO->SAP Reference IMG Activity->Additional Information-Activity Importance (You can data like below picture ).

4. If you want any T.Code for any IMG activity then you don’t want think more as simple you can get all T.codes in SPRO level.

For getting above info please go by path as below,

SPRO->SAP Reference IMG Activity->Additional Information-> Additional Information-> Display->IMG Activity  ( You can data like below picture ).

5. As above like any IMG Activity is Critical or no-critical position is find out by SPRO level.

For getting above info please go by path as below,

SPRO->SAP Reference IMG Activity->Additional Information-> Critical Activity( You can data like below picture ).

Note : I think, might be know all users this way but only for begging folks I am posting here .

If you have any Issues on this Please let me know .

Created by,

Narendra Konnipati

Hi everybody,

I made a general data flow for SD module. If, you find  Text Removed

Many Thanks / Himanshu Gupta

Message was edited by Lakshmipathi

Please dont add such texts and go through the forum rules before posting

Free Goods determination happens in Sales Order based on Free Goods Condition Records maintain in T-Code VBN1.

Now while creating Delivery, system just copies the Main Item quantity & Free Goods Item Quantity from Sales Order & does not access the Free Goods condition again.

In case of complete (single) Delivery for one Sales Order, there is no problem because full quantity of main & free item is delivered at one go.

But let us imagine a scenario where partial deliveries are done.

For Example, say in a Sales Order:

Main Item – 100 Tons

Free Item  - 10 Tons

Delivery:

Main Item  - 50 Tons (system proposes 100 Tons, which is reduced to 50 Tons)

Free Item – 10 Tons (system does not reduce the Free Goods proportionately)

As seen above, system does not reduce the Free Goods quantity even if the Main Item quantity is reduced in Delivery.

To control this situation SAP System has given following options to control partial Deliveries (to be maintained in under “Free Goods delivery Control” VBN1 Condition Record):

   - Delivery takes place regardless of main item

A - Delivery only if main item is partially delivered

B - Delivery only if main item is fully delivered

C - Delivery if main item is part. delivered, only with main itm

E - Delivery proportional to quantity in main item

Normally E "- Delivery proportional to quantity in main item" is maintained to ensure that any reduction to main item will make proportionate reduction in Free Items. But the Main Item & Free Item quantity field is modifiable & user can further increase the Free Goods Item quantity to Sales Order Free Goods quantity.

To control the above, we have recently made the Free Goods Item Quantity Non-Modifiable in Delivery document by inserting a ABAP code in Badi - LE_SHP_DELIVERY_PROC.

ABAP Code:

METHOD if_ex_le_shp_delivery_proc~change_field_attributes.
  ....       sy-tcode = 'VL01N' OR sy-tcode = 'VL02N'.
      ....         IF screen-name = 'LIPSD-G_LFIMG'.
                         IF is_lips-pstyv = 'TANN'.
            screen-input  = 0.
            screen-active = 1.
                 ......
ENDMETHOD.

This will ensure that the Free Good Item in Delivery Document is Non-Modifiable & any reduction to Main Item quantity will reduce the Free Item Quantity proportionately, which cannot be changed by the users.

Hi Friends,

Here i am trying to show you, how we add partner function to the standard report selection criteria.

Requirement :i want to run report to  generate  list of Quotations  with ship to party instead of Sold to party, but standard report VA25 have only partner function sold to party as selection field, now we want to enhance the VA25 report to include SH(Ship to party) as a selection criterion.

Now the system output:

• Go to Tcode VA25 , Only sold to party selection field available.

• Click on Partner function tab, a popup appear with select partner function.

• If you want to change the partner function(SP to SH) system will not allow and give warning massage.

Configuration steps for retired output:

• SPRO --> Sales& distribution --> Sales --> List --.> Set updating of partner index.
• Go to new entry and select required transaction group ( in our we select 2- quotation) and save the record.

• Go to Tcode VA25 and select partner function tab, now you should able to see partner function SH(Ship to party)

• Now you should able to execute VA25 report with partner function SH.

• But system will give the following massage, this is standard behaviour now we have to updating the historical data.

Updating the historical data:

Go to Tcode SE38 and enter program name “RVV05IVB”

• Execute the programme .

• Select the” partner index” filed in sales document and execute.

• Now go to Tcode VA25 and enter ship to part name and execute, we will get the total historical report .

Hope you like my detailed explanation

If you still have any doubts or further clarification reuired , plz let me know.

Regards,

Patchala.

Hi friends,

We had a requirement from our client wherein they want some notifications if a critical sales document has been changed?

This can be activated simply by using a function within the “Services for object” icon. You can activate the services for Object icon with the user parameter “SD_SWU_ACTIVE” and the value “X“.

Transaction Code : SU3

Further one should then subscribe to changes to that object, by going into the sales document in change mode and selecting the icon in the top left and the

menu path: My Objects–>Subscribe/Cancel Object.

The result:

Any modification to the order will result in a notification to your Business Workplace. (Transaction SBWP). This is a great tool for monitoring of sensitive sales documents.

Rebate Processing

Rebates: Rebate agreement is a special agreement granted to the customer on a specific volume of sales over a specific period of time.

Configuration Path:

IMG>SD>Billing>Rebate Processing>Rebate Agreements>Define Agreement Types>

Step 1: Define Agreement Type

Select"Define Agreement type " from choose activity,double click on it

Select an Agreement click on copy button and rename it

here I selected standard and renamed “0002-Material Rebate” to “Z002- Material Rebate-AA11”

Step 2:  Condition Type Groups

  2.1:Click on Define condition Type groups

Click on New Entries

Enter your Copied Condition Type group which you created and Maintain “Blank” for Category of the condition type group

   Step 2.2:  Assign Condition Types /tables to Condition Type groups

Click on New Entries

Assign Condition Type“Bo02” and Condition Table“1”to your Condition Type Group”Z002”

Step 2.3: Assign Condition Type groups to rebate agreement types

Click on it, Assign Condition Type group to Agreement Type

Step 3:   Condition Technique for Rebate Processing

Click on it

  Same as like Pricing Procedure configuration

Step 3.1: Select Maintain condition table for Rebates

Select Maintain Condition Tables for Rebate and Click on Choose

Based on requirement we can create new condition table

Save and exit (if anything created)

3.2: Maintain Access Sequence

Select Maintain Access Sequence

Click on Choose, Go to New Entries and Maintain Access Sequence

Maintain “1” Relevant for Rebates

Step 3.3: Define Condition Types:

Choose Define condition types

Select it and click on Choose

Rebate condition types (BO01, BO02, BO03, BO04, BO05, BO06)are available in Standard SAP

Assign Access sequence to condition Type (if copied)

Step 3.4: Maintain Pricing Procedure:

Select Maintain Pricing Procedure and click on Choose

Choose Standard or copied Pricing Procedure by use

Click on Position Button left side Dialog Structure

Make sure that Rebate condition types must available in (copied) pricing procedure

With Requirement-24 (only in Billing Document)

Account Key - ERB

Accruals - ERU

Step 4: Account Determination for Rebates

(If your are good at Account determination Procedure configuration no need to fallow this)

The same process like Account Determination Procedure

Step 4.1: Define A/C keys

(Standard keys available in SAP)

ERB -Rebate Sales deduction

ERU –Rebate accruals

Step 4.2: Assign Account Keys to our Pricing Procedure

In standard pricing procedure it’s available

Steps 901 to 905

Step 4.3: Maintain Access Sequence

(standard already created like Accounting Determination Procedure)

Step 4.4: Define Account Determination Types

Assign access sequence to Condition type

Step 4.5: Assign G/L Account

Choose table 1-customer group/Material Group/Account Key

Click on Assign button and Maintain G/L Account Provision Account

Step 5: Activate Rebate Processing

IMG>SD>Billing>Rebate Processing>Activate Rebate Processing

Click on “Activate Rebate Processing”

Select “Billing Documents for Rebate Processing” in Choose Activity.

Step 5.1: Select Billing Document for Rebate Processing

T-Code: OVB0

(Or) T-code: VOFA

Enter billing Document Type and put check mark for Relevant for Rebates

Go back, Select “Activate Rebate Processing for Sales Organizations”

Step5.2: Activate Rebate processing for sales organization

Click on Choose

(Or)Go to Enterprise structure

T-code: OVX5

Select your sales organization

Put check mark for Rebate process Active

Step 5.3: The payer must be relevant for rebate processing.

Go to XD01 or XD02 Payer customer master record

Go to sales are data tab then choose Billing tab put check mark for “Rebates”

Step 6: Create Rebate Agreement

T-code: VBo1 or SAP Easy Access Path

SAP Menu>Logistics>Sales and Distribution>Master Data>Agreements>Rebate Agreement

(VBO1-Create/VBO2-Change/VBO3-Display)

Choose created one (Ex: Z002)

Specify the rebate recipient [Customer master payer number]

Specify the validity period of the agreement

Specify the agreement status: Blank [] = Open

Specify the verification level [F] = Display totals by Payer/Material

Then click on Conditions on top

Maintain (Accruals amount) condition record for material rebate how much rebate we want to give it to the customer

If we click on scales button

Here I maintained for each product 1 rupee

go back

save it.

With this configuration part is completed

Step7: create sales order

T-code: VA01

Specify Organizational details

Press F8(document Complete)

Check item conditions

Save it

Step 8: Create Delivery

T-code: VL01n

Step 9: create Billing document

Check ITEM conditions BO02 will display in conditions tab because we maintained requirement ‘24’ in our pricing procedure

save it

Now Rebate Settlement to customer

Step 10: Go to VBo2 rebated agreement

Enter rebate agreement which we created

Ex:  34

Check agreement status to ‘B’ 

On the menu bar choose “Rebate Payment”

Here Customer is eligible for 50 Rs rebate accruals amount

If we observe Verification Levels

Will get details of payer customer master total rebate accruals amount 

We can settle the rebate amount by manual or automatic

Manually we can select the customer eligible amount

Then we can save it

It will create automatically credit memo request

Here I have chosen 5Rs/- and save it

We will get the message like this bottom of the screen.

Or if we want to give full settlement to the customer click on

It will create automatically Rebate Request for Manual Accruals for entire eligible pending amount.

It will happened in the back ground

If we want to check that go to this path or Click T-code: VOV8

Select any one of the above document type

B1, B2, B3 OR B4 click on details icon

Coming back to Rebate credit memo request

Back ground automatically created we can check these details by using T-code: VA03

Now create Billing Document by using sales order number

Check the conditions

Save it

Billing document will be generated

Rebate accrual amount 5Rs

Check Accounting Document

General ledger view

With this Rebate agreement process is completed.

Note: configured in IDES system,Information purpose only.

Regards,

Krishna.

Many times we have a situation wherein we want to know is  there is a pricing conditions change report in SAP which give details about all the changes happeend to a pricing condition type.

Report - RV16ACHD from SE38 or SA38 to address above points.

This report gives you the ability to check the before and after values for condition records for a condition type.

You can limit the selection criteria to be table specific if required, in addition to using a date range.

You are also able to select changes made by a specific user ID, or even changes made when a specific transaction code was executed.

Execute Report and give selection inputs asper your requirement .

Report output will be detail about all the changes to a condition type

  Date / Time/User/Transaction/Old and New Value .....

Thanks

This document will help you to list Sales orders in SAP by ship to party or any other partner function .

Once can easily do this in VA05.

When in VA05 change the Search parameter from Sold to Party to Ship To Party by selecting the “Partner Function” button Ctrl+F10.
Then use the other selection parameters as required.

The resultant lists can be downloaded/exported from the ALV grid.

If you dont find SH or any other partner function in in VA05,then it can be customised by adding it in the below mentioned menu path

IMG–>SD–>Sales–>Lists–>Set updating of partner index

Add SH or other partner to Transaction Group ’0′.

Then you can get a report based on Ship to Party or other partner function in VA05.

Result :
It is a really a great functionality in SAP to List orders based on different partner functions.

Hello All,

Recently my client launched a new Product which was pushed to existing Dealers along with existing Products but the Payment Terms for new Product was different than existing Products.

For Example, A Mobile handset manufacturing company has launched a new Handset & it is selling in large numbers. Due to this newly launched Product, the earlier Products (which are lying in Stock) are not in demand & sales are slow. Thus this Company comes out with a scheme that for every 4 latest Handset, Dealers will have to Purchase of 1 older model Mobile. Payment Terms for Latest Mobile will be immediate & for older model Mobile will be after 30 days.

Now how to handle scenario like this where in single Sales Order for same Sold-to-Party & Ship-to-Party, payment terms are different for each Material.

SAP has given facility of maintaining Payment Terms in Condition Records of Materials as shown below:

Payment terms mentioned in Condition Record will be determined for the respective Line Item while creating Sales Document & will overwrite the Payment Terms mentioned in Customer Master Record.

Point to be noted: While we can successfully create Sales Order & Delivery with multiple Line Items & Separate Payment Terms, but there will be Invoice split based on Payment Terms. Because Payment Terms is Header Level field in Invoice.

A pre-requisite – In Item Category (T-Code VOV7) Business Item Check Box should be ticked, which will allow separate Business Data in Sales Order Header & Item.

Hope this is useful.

Thanks,

Today User raise a problem that quantity correlation function can not be used in delivery, but can be used in sales order, so I did some testing and summarized here.

Quantity correlation function is when you change quantity in high level item, quantity of sub-item will be changed in proportion automatically.

There is two factors have effect on quantity correlation function. 

• Sales BOM linkage (VBAP- UEPOS), items have high-sub item link.

• Delivery group (VBAP- GRKOR)

   In Sales order (Sales BOM linkage and delivery group can be updated manually)

1. Sales BOM linkage existed with delivery group, quantity correlation function is active.
2. Sales BOM linkage existed without delivery group, quantity correlation function is active.
3. Delivery group existed without sales BOM linkage, quantity correlation function is inactive.

In Delivery (Sales BOM linkage can be updated manually, delivery group can not be updated):

1. Sales BOM linkage existed without delivery group, quantity correlation function is inactive
2. Sales BOM linkage existed with delivery group, quantity correlation function is active.
3. Delivery group existed without sales BOM linkage, quantity correlation function is inactive.

Major difference is quantity correlation function is
inactive in delivery if no delivery group maintain even Sales BOM linkage is existed, debug result as below:

SE38: MV50AF0K_KORR_MENGEN_AENDERN, there is a check of delivery group.

“CHECK xlips-grkor > 0.”

Conclusion: Sales BOM linkage is foundation of quantity correlated function, but if you want to active this function in delivery, you have to use delivery group at same time.

PS: Automatic Sale BOM linkage and delivery group function are control by item category (VOV7)

With best regards

Liu Jian

Many times we have a situation wherein after completing the settings for credit management you want to know is there is a report in SAP which give details about 
Analysis of Sd document regards to credit mangement.

Report - CHECK_CM  from SE38 or SA38 to address above point.

Once you have completed the customization settings for credit mangement .

And further if you want to check how credit mangement has been processed for a sales document.

  Then its possible by a standard report provided by sap to analysis of sd document regards to credit mangement Analysis

      Report : CHECK_CM

Execute Report and give selection inputs( Sales order or Delivery Number) asper your requirement .

Report Output as

   All credit related checks that has been performed for the sales document

Thanks

Integrations aspects of SAP Service Management with other modules of SAP

Business Processes in Service Management

I. Service with Time & Material Billing

Service is provided after customer reports the problem. Technician is dispatched to customer’s location where
equipment is located. After work is performed and repair is finished, customer is billed based on time and material spent on repair. Quotation may be given to customer based on estimated costs of repair if required.

II. Service under Contract

A Service Contract is signed with
customer that details scope of services covered within certain period. Any
service performed in that period is bound by terms of the contract. Service
could be a planned activity e.g. preventive maintenance or  Service could be provided after customer
reports the problem e.g. corrective maintenance. Technician is dispatched to
customer’s location where equipment is located. Customer may or may not be
billed based on terms of the contract.

III. Service under Warranty

When new equipment is sold to customer
typical Warranty
is applicable for that equipment. During this warranty period service
is provided without any charge.  Within
warranty period replacement may be given to customer in case equipment is not
repairable. Typically costs of repair when product is under warranty are
tracked separately than other repairs since they are closely related to product
design and performance.

IV. Returns Repair

Sometimes it is not possible to carry out
repair at customer’s site for some reasons e.g. repair requires specialized
machinery not available at site. In such cases equipment is brought to repair
facility. Once repair is finished same equipment is then sent back to customer.
During entire process, equipment is present on company’s premises but it is
legally owned by customer. Customer may be billed a fixed price or based on
resources consumed.

SAP Enterprise Structure

• Company Code
• Sales
  Area
• Sales Organization
• Distribution Channel
• Division
• Plant Maintenance Planning Plant
• Storage Location

Important Master Data Objects:

Master Warranty :

Transaction codes – BGM1- Create/2 Change/3 display.

Warranty Master is used by Plant Maintenance and Service Management only.

Warranty Master records information about duration of warranty and how it is applied.

Warranty Master is not directly used in any scenario. Warranty is applied to an
equipment after it is sold to customer.

Functional Location :

Transaction codes – IL01-create/2 change/3 display.

Functional Location represents customer location where actual equipment is located.

Functional Location hierarchy can be used to create structure of actual physical location.
E.g. Rooms on floors inside building within campus.

Functional Location tells technician where to look for equipment when they go onsite.

Each functional location is assigned basic partners – sold-to, ship-to and bill-to.

Equipments are ‘installed’ at functional locations.

When an invoice is created, sales revenues, sales deductions and taxes should automatically be posted to the relevant accounts in FI (Financial Accounting).

The system can forward billing data in invoices, credit and debit memos to Financial Accounting and post them to the appropriate accounts.

Customizing by SPRO

1) Master Data Relevant For Account Assignment

You can set the system so the account determination is dependent upon the following master data fields:

- Account Assignment Groups (for material) in the material master record

  (Table: TVKM; Transaction: OVK5) – Sales org 2 Tab

- Account Assignment Groups (for customer) in the customer master record

  (Table: TVKT; Transaction: OVK8)  - Billing Tab

2) Define Dependencies Of Revenue Account Determination

- Here you can define a combination of criteria on which account determinationshoulddepend  (Condition Tables - Transaction: V/12 create, V/13 change and V/14 display table)

3) Define Access Sequences And Account Determination Types

    - Maintain access sequences for account determination

      (Table T682, Transaction: V/10 Standard: Access sequences --> KOFI)

    - Define account determination types

       (Table T685Transaction: V/09)

4) Define And Assign Account Determination Procedures

    Define Account Determination Procedures (Table T683, Transaction: V/11)

    ALL Condition Types which should be used have to be assigned in the procedure

    Standard: Condition Types  -->  KOFI Account Determination

         (Normal accounts)

    -->  KOFK Account Determination with CO

         (Different accounts, which allows to post to sales order VBELV)

To avoid errors during the account determination we recommend to assign both Condition Types (KOFI and KOFK) to the Account Determination Procedure

Account determination procedure has to be assigned to every Billing    Type which is used in your system (Table TVFK, Transaction: OV33)

5) Define And Assign Account Keys

   Define account keys(this is in FI)

(Table: T687; Transaction: OV34)

   important account keys predefined in the standard SAP R/3 System

      ERL Sales revenues

      ERS Sales deductions

      ERU Rebate accruals

      ERB Rebate sales deduct.

      ERF Freight revenue

      EVV Cash clearing

      MWS Taxes

    Assign account keys

(Table: T683S; Transaction:  OV35)

or

assign the account keys in field KVSL1 and  KVSL2 in the pricing

procedures (Table: T683S; Transaction: V/08)

     E.g.  Account Key ERU (Rebate accruals) and B01 (Rebates) have to be maintained       in field ‚KVSL2‘ 

6.) Assign G/L Accounts

(Table: C001; Transaction: VKOA)

Forcomponent SD-SLS-SO-TP therearesome FAQ Notes availablewhichareoften a goodchoicetostartwith:

498162 : FAQ: Third-party order processing in purchasing

549365 : FAQ: Scheduling for third-party and individual PO

549583 : FAQ: Order confirmation status of 3rd-party & individual PO

549818 : FAQ: Billing status for third-party items in sales order

549972 : FAQ: Rejecting third-party or individual PO items

550192 : FAQ: Changing third-party and individual PO items

550362 : FAQ: Special problems for third-party and individual PO

550388 : FAQ: Customizing of third-party and individual POs