To track the line item to which the billing plan date changed.

Hi All.
I have a requirment of tracking changes done for the billing plan date and whenever i change the billing plan date it will be reflected in the FPLA table. But i was not able to track to which line item of the subscription/order the billing plan date changed.
In the FPLA table there is a relation to the VBELN(subscription/order) only not POSRN(line item) is there.How can i track to which line item it got changed.
Thanks for your help.
Thanks,
Neslin.

Hi,
There should be entries in FPLTC for FPLNR found in table FPLA. Try from SE16, enter FPLNR preceded by zeros so that the total length is 10 and execute.For example, FPLNR is 10, enter 0000000010.
Hope it helps.
Regards,
Nupur

Similar Messages

To track which line item the billing plan date changed.

Hi All.
I have a requirment of tracking changes done for the billing plan date and whenever i change the billing plan date it will be reflected in the FPLA table. But i was not able to track to which line item of the subscription/order the billing plan date changed.
In the FPLA table there is a relation to the VBELN(subscription/order) only not POSRN(line item) is there.How can i track to which line item it got changed.
Thanks for your help.
Thanks,
Neslin.

Hi,
There should be entries in FPLTC for FPLNR found in table FPLA. Try from SE16, enter FPLNR preceded by zeros so that the total length is 10 and execute.For example, FPLNR is 10, enter 0000000010.
Hope it helps.
Regards,
Nupur

How to make plant default on the line item along with the item category

Hi All,
I want to default Plant on the line item along with the item category.In order to meet the following scnario.
1. I have two plants,first plant is maintained for the valuated item and the second plant is maintained for the non valuated item (Free Goods).
Whenever user is entering an item in the sales order for which corresponding free goods item is maintained in the master record.System is proposing two lines items in the sales order.
First line item is the main item which appears along with the Plant 1 which contains valuated items
Second line item is for the Free of charge item which is being proposed from Plant 2, which contains the non valuated items.
I want that the system should always propose Plant 1 with main item and Plant 2 with the Free of Charge item by default. (Along with the item category TAN and TANN)
Rahul

Delivering Plant is determined in the following order
1. Customer material info record.
2. Customer master
3. Material master.
Use one of them an default your plant.
I think in your case you can use the materila master which will give an item level plant different. The other two will default the plant at the header level.
regards
jude

How to add the line item text in the Ledger line item report

Hi SAP Gurus,
I having one requirement from the user. He wants the line item text which we will enter in FB60/FB70/FB50 has to be shown in the Ledger line item report. Right now this field is not available. Is there any possible we can make this line item text in the ledger line item report i.e. FBL1N/FBL3N/FBL5N?
advance thanks for the help.
Regards,
Deva.

Hi,
You can do the below to get this. (You can change the names of the function modules as per your wish/ organization naming convention):-
Step 1:-
Create function module Z_GET_SGTXT as below:-
Import:-
BELNR LIKE BKPF-BELNR
BUKRS LIKE BKPF-BUKRS
BUZEI LIKE BSEG-BUZEI
GJAHR LIKE BKPF-GJAHR
Export:-
PRCTR LIKE BSEG-SGTXT
FUNCTION Z_GET_SGTXT.
""Local Interface:
*" IMPORTING
*" VALUE(BELNR) LIKE BKPF-BELNR
*" VALUE(BUKRS) LIKE BKPF-BUKRS
*" VALUE(BUZEI) LIKE BSEG-BUZEI
*" VALUE(GJAHR) LIKE BKPF-GJAHR
*" EXPORTING
*" VALUE(SGTXT) LIKE BSEG-SGTXT
SELECT SINGLE SGTXT FROM BSEG INTO SGTXT WHERE GJAHR = GJAHR
AND BELNR = BELNR
AND BUKRS = BUKRS
AND BUZEI = BUZEI.
ENDFUNCTION.
Step 2:-
Then create the Function Modules as below:-
Z_LINE_ITEMS_GET_SGTXT (Copy of SAMPLE_INTERFACE_00001650)
FUNCTION Module Z_LINE_ITEMS_GET_SGTXT.
""Local Interface:
*" IMPORTING
*" VALUE(I_POSTAB) LIKE RFPOS STRUCTURE RFPOS
*" EXPORTING
*" VALUE(E_POSTAB) LIKE RFPOS STRUCTURE RFPOS
Initialize Output by using the following line
E_POSTAB = I_POSTAB.
E_POSTAB = I_POSTAB. "<-- important
CALL FUNCTION 'Z_GET_SGTXT'
EXPORTING
BELNR = I_POSTAB-BELNR
BUKRS = I_POSTAB-BUKRS
BUZEI = I_POSTAB-BUZEI
GJAHR = I_POSTAB-GJAHR
IMPORTING
SGTXT = E_POSTAB-SGTXT
EXCEPTIONS
OTHERS = 1.
ENDFUNCTION.
Step3:-
Transaction FIBF:-
Settings -> Products -> of a Customer
SGTXT Text in Line Item Display Active
Settings -> P/S Module -> of a Customer
00001650 SGTXT Z_LINE_ITEMS_GET_SGTXT
Step 4:-
Create the layout for FBL*N with display of the TEXT.
Regards,
Gaurav

Captuing the Line Item info from the ALV Grid

Hi Abapper,
Suppose I have an OO ALV Grid displayed on the Screen by using SET_TABLE_FOR_FIRST_DISPLAY.
Now, suppose the grid contains 5 fields of the database table.
I have to display the 6 th one of tht table by capturing the line item on which I click into the grid and select the 6th one and displayed.
But how to capture the line item of the grid, when i click any rows in the grid.
Please reply.
Regards,
Rahul

Hi Rahul,
Two methods are available,
1) Define the double_click method, or
2) Implement the HotSpot and User_command method.
i_callback_user_command           = slis_ev_user_command
form user_alv_command using r_ucomm like sy-ucomm
                            w_selfield type slis_selfield.
*Routine called when user invokes a command not handled by the ALV
case r_ucomm.
    when '&IC1'. "Hot Spot Click
       read table itab index w_selfield-tabindex.
    when others.
endcase.
endform.                    " USER_ALV_COMMAND
Kind Regards
David Cooper

How to add the line items while running the VA01

HI All,
I want to add the line items while I am running the VA01 t-code(In run time).Could anybody give the FM to create the line items....Its urgent

Hi ,
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
regards
P.

BAPI_PO_CHANGE to update the Price for the line item not updating the Price

Hi,
I am using BAPI_PO_CHANGE to update the Price for the line item. This BAPI is not updating the Price. I am using external cummit also, but the BAPI is not updating price.
I am passing following data to the BAPI.
Plant: CQ11
PO Material Price
4500002142 TEST_BATCH 12
Please provide suggestion.
Regards,
Jubin.

Hi,
check this link...this has sample code
[http://www.sap-img.com/abap/sample-abap-code-on-bapi-po-change.htm]
Regards,
Surinder

How to Close a Purchase Order line Item for GRN W/O Deleting the Line Item

Hi,
I want to Close a line item for Goods Receipt in a Purchase Order. How Do I do this?
My Requirement is that the system should not allow for Goods Receipt for the Line Item.
I know of 2 options which are difficult to Implement.
1) I delete the Line item
2) Put the delivery Completed Indicator - For this the system still allows for GR
any Other way of Closing the line Item
NS

Hi, you can close the Line item by, doing partial GRPO, i.e if u use the Copy From option in GRPO, there comes a Draw docuemnt wizard, there you can choose one line item, and then put GRPO for that line item,
The Wizard comes only in the Copy From option,
Close the Line item, by right clicking on that Line item and then 'close Row'
Edited by: Gayathri Panneerselvam on Dec 19, 2008 10:25 AM

How to get the change mode option for the line items in SC

Hi Everybody,
1. when the SC has 2 line items and in that if both the line item are rejected by the approver and the requester is receiving it for accept changes and when he click on the change button and wants to change the line items of both the rejected one, the change is enable and the requester can do the changes in the line items of the shopping cart which is working fine. but in the other case
2. when the SC has 2 line items and in that if any one of the line item is rejected and other one is approved by the approver and the requester is receiving it for accept changes and when he click on the change button and wants to change the line item of the rejected one, the change is getting disabled but for the approved line item the requester can able to do the changes.
so can anyone help me out how to solve this issue that if any one line item is rejected in the shopping cart also it should get the editable mode when the requester wants to do any changes.
thanks in advance.

Hi Everybody,
1. when the SC has 2 line items and in that if both the line item are rejected by the approver and the requester is receiving it for accept changes and when he click on the change button and wants to change the line items of both the rejected one, the change is enable and the requester can do the changes in the line items of the shopping cart which is working fine. but in the other case
2. when the SC has 2 line items and in that if any one of the line item is rejected and other one is approved by the approver and the requester is receiving it for accept changes and when he click on the change button and wants to change the line item of the rejected one, the change is getting disabled but for the approved line item the requester can able to do the changes.
so can anyone help me out how to solve this issue that if any one line item is rejected in the shopping cart also it should get the editable mode when the requester wants to do any changes.
thanks in advance.

Splitting the Line items in Transaction LB02........

Hi Frnds,
            I would like to know how to proceed further....afetr entering into standard transaction LB02, the user wants to split the line items depending on the quantity what he has enterd in the custom screen which i developed.
           Here am able to get the data in background necessary to goto standard transaction. After entering into the standard transaction how to split the line items.
Functional Requirement
In the screen, which i developed...
The user enters material no...
-->Matl qty & matl desc will be displayed....
-->Then user enters the bin no.   and the qty he wants to keep in that particular bin.
-->Here depending on the qty the user has entered it has to reflect in the Tcode LB02.
-->For example, total qty displayed in the custom screen after entering the matl no. is 20 From this qunatity, the user enters the quantity as 10 which is not GE to that qty (20) which we got from database.
-->Now this has to be replicated in the standard transaction in such a way that..the line items should also split according to the qty the user enters.......it may be upto n no. of line items.....and the bin no. should also be entered into the stnd Tcode LB02 at the unloading point field......
Thanks & Regards
Message was edited by:
        Badri Thiriveedhi

Managed to find an Enhancement Point in the Standard SAP Code and hence the Issue is resolved.
Thanks and Regards,
Venkat Phani Prasad Konduri

Amount in Bar Code is incorrect;Amount in the line item can be used instead

We have a problem in our Brazil company code.
When we have a document with value higher than 5,000.00 BRL it is subject to Pis/cofins tax. In the Boleto (paper) document the amount is after tax deducted. But we see the full amount in the Vendor line item in SAP
When the system reads the bar code and saves this code in the vendor line item during the document change we get a warning message no."8B797: Amount in Bar Code is incorrect;Amount in the line item can be used instead".
And the amount in the Barcode line automatically adjusts itself to the line item amount which is the pre-tax amount (full amount).
Example: Amount in the SAP Invoice doc is R$ 6,268.72
Amount in Boleto (paper) R$ 5,977.22 (after deducting PIS/COFINS) - This amount appears in the bar code but once we press enter after the warning message it automatically adjusts to R$ 6,268.72 .
We tried few notes like 784748 to apply but it says it is obsolete. We are on ECC 6.0 Release level 11.
Regards.,
Raj/

answered through SAP note 784748

Tracing the line item change in a accounting document

We have to send accounting document line items details which have been created or changed to non-SAP system.
I am looking for way to identify the line items which have been changed as I don't want to send the other line items of the accounting documents which are not changed.
Thanks.

Shailendra,
You've hit the nail on the head - CDHDR and CDPOS are the central repository tables that contain all changes - wherever logged.
There's no other way.
P.S.: I'm assuming you know how to extract data from these tables - so am not going into it.
Remember to assign points if found useful.
Regards
Gulshan

Defaulting the Sotrage location for all the line items in my sales order

Hi,
I have a scenario to default the storage location automatically in my sales order for all the line items. It is not going to change for a particular sales org. Dist. channel & Division combination. Can you pls. suggest me a solution for this.
Thanks
Ghanesh.

Hi,
You can default the storage location by using the below user exit
Storage location
Auto determination of storage location as u2018XXXXu2019 for sales order
Include - MV45AFZB
Form - USEREXIT_SOURCE_DETERMINATION
IF (VBAK-AUART = 'XXXX' and VBAK-VKORG = 'XXXX' and VBAK-VTWEG = 'XX').
VBAP-LGORT = 'ABCD'.
Regards,
Gopal.
Edited by: Gopalakrishnan S on Feb 25, 2010 7:35 AM

How to retrieve the Line item Text

Hello,
I need to retrieve the Line item Text in the PO (Material PO text). Can anyone provide me a sample code? i need to display this in a smartform.
I could not retrive it from the Function Module READ_TEXT.
Can any one help me regarding this?
Regards,
kvsskirankumar

HI,
Use function module READ_TEXT to fetch PO line item text by passing id, language, name and object.
For Ex:-
CALL FUNCTION 'READ_TEXT'
EXPORTING
    CLIENT             = SY-MANDT
    id                      = 'F01'
    language          = 'E'
    name                 = << concatenate PO number & line item>>
    object                = EKKO
tables
    lines                   = g_t_ltext.
Thanks & Regards
Sudheer Madisetty

Make changes to the line item depending upon doc type n sp. GL ind in F-48

I want to make changes to the line item depending upon the document type and special GL indication for the transaction code F-48.
Depending upon document type and special GL indicator i want to calculate the work contract tax during simulation in transaction code F-48.

Hi,
You want to deduct WCT when you use particular document type and special gl indicator.
I just want to know the reason why you want to determine the WCT based on the above conditions.
I created WCT as withholding tax types and assigned to vendor master. So when the user booking transactions he will choose the respective WCT tax type and tax code so system will deduct the amount and the same updated in WITH_ITEM.
Or you made a down payment request through T.code F-47 and when you want to book the actual transaction in F-48 then choose line item from down payment request.
Give me your requirement in clear if the above is not clear
Regards,
Sankar

To track the line item to which the billing plan date changed.

Similar Messages

Maybe you are looking for