Skip to main content

Sales Item Category Controls - Part 2

Pricing

Indicates whether the system automatically carries out pricing at the item level.


Blank No pricing

This is used for Text items and Items not relevant for pricing scenarios

X         Pricing standard

The system carries out pricing for standard items in a sales order.

A         Pricing for empties

B         Pricing for free goods (100% discount)

This is used for free Goods Items

Schedule Lines Allowed

Schedule lines determines the delivery date and quantity. Enabling this check box, Will display schedule lines at sales order item level else schedule lines tab will not be displayed  For standard item, schedules lines exists but where as for text or service items this is not required to be enabled as schedule lines are not required.

Item Relevant for Delivery

This checkbox is enabled for the items which don't have schedule lines and require delivery processing. Ideally, this is used for text items and Value Items.

It serves only for the information purposes during delivery. 

Credit Active

Select this field if the values of the item need to be updated to the customer credit. Even though at document type level if credit management is not enabled, if the item level check is enabled item values will be adjusted against the customer credit.

Determine Cost

 This indicates whether system need to determine cost of an item during item pricing at sales order item level.

Enabiling this field is the pre-requisite in triggering of the VPRS condition type in pricing.

Structure Scope

This field controls how the kit items need to be processed at sales order level. 

Blank Do not explode material structure

By default this field will be blank i.e, not enabled for BOM explosion

A         Explode single-level bill of material

This field is enabled for a kit item with single level BOM i.e., BOM header item is not part of any othe BOM explosion.

B         Explode multi-level bill of material

This field is enabled for a kit Item with Multiple level BOM i.e., BOM header item is used as a component in other BOM.

Comments

Post a Comment

Popular posts from this blog

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more