Issue with sorting of TO line item while using LM05 / LM07

Hi,
We have found an issue in using LM05 / LM07 trnasactionwhile performing picking activity using the RF transaction.
1. Transfer Order is created for the same Material and Batch Combination with multiple line items. So when we display the TO the materials appear in the sequence of TO line item say 1, 2, 3, 4, 5 etc.
2. When we try to confirm the transfer order using LM05 the system is not picking the line items in the order that the TO was created. It is pickinga a random line item from the order and selecting an item from the lower line items of the TO's.
We have debugged and found that there is no specific sort sequence which is changing the sequence of line items as all the sort eliments have the same values except that there are few empty fields. The statement where the sort sequence is changing is 'SORT TMP_SORT_TAB BY NLTYP SORLP NLENR MATNR CHARG' but my concern is it is not sorting by this sequence specified in the code after execution.
If anyone has seen this kind of an issue and has a solution please let me know.
Thanks in Advance,
Harish

As for std SAP ME59N - make sure there is not rounding value is activated in the Material master as well as info record
If this is not the case than check any custom code is activated for ME59N
becuase generally in many compnay when they use ME59n they don't want the same material from diff PR to create the diff line item in the PO so using the custom logic in the user exist they trick the code
it might be the case for you where you have issue.

Similar Messages

Problem in uploading multiple line items while Creating sales order by BAPI

Hi experts , Im able to create sales order with one item while using this program, but the problem is when iam having multiple items or multiple sales order , iam not able to createthe line items , though its creating sales order header , Iam copy pasting my code , please add the additional code to my code to take more than 1 line items ,This is urgent requirement . Points will be rewarded for answers , Thanks in advance
*& Report Z_SO_CREATE_BAPI
REPORT Z_SO_CREATE_BAPI.
DATA: i_header TYPE bapisdhd1 occurs 0 with header line.
DATA: i_details TYPE bapisditm OCCURS 0 WITH HEADER LINE.
DATA: i_partner TYPE bapiparnr OCCURS 0 WITH HEADER LINE.
DATA: i_return1 TYPE bapiret2 OCCURS 0 WITH HEADER LINE.
DATA: i_return2 TYPE bapiret2.
data : ORDER_HEADER_IN like BAPISDHD1.
data : ORDER_ITEMS_IN like BAPISDITM occurs 0 with HEADER LINE .
data : ORDER_ITEMS_INX Like BAPISDITMX occurs 0 with HEADER LINE .
data : RETURN like BAPIRET2 occurs 0 with header line.
data : ORDER_PARTNERS like BAPIPARNR occurs 0 with
header line.
DATA : ORDER_KEYS LIKE BAPISDKEY OCCURS 0 WITH HEADER
LiNE.
data : ORDER_SCHEDULES_IN like BAPISCHDL occurs 0 with
header line.
data : ORDER_SCHEDULES_INX like BAPISCHDLX occurs 0 with
header line.
data : BEGIN OF TAB OCCURS 0,
 SRNO(4),
 DOC_TYPE like ORDER_HEADER_IN-dOC_TYPE,
 SALES_ORG LIKE ORDER_HEADER_IN-SALES_ORG,
 DISTR_CHAN LIKE ORDER_HEADER_IN-DISTR_CHAN,
 DIVISION like ORDER_HEADER_IN-DIVISION,
 REQ_DATE_H(10),
 PURCH_DATE(10),
 PMNTTRMS LIKE ORDER_HEADER_IN-PMNTTRMS,
 PURCH_NO_C LIKE ORDER_HEADER_IN-PURCH_NO_C,
 ITM_NUMBER like BAPISDITM-ITM_NUMBER,
 MATERIAL LIKE ORDER_ITEMS_IN-MATERIAL ,
 PLANT LIKE ORDER_ITEMS_IN-PLANT,
 TARGET_QTY LIKE ORDER_ITEMS_IN-TARGET_QTY,
 ITM_NUMBERX like ORDER_ITEMS_INX-ITM_NUMBER ,
 MATERIALX LIKE ORDER_ITEMS_INX-MATERIAL ,
 CUST_MAT22 LIKE ORDER_ITEMS_IN-CUST_MAT22,
 PLANTX LIKE ORDER_ITEMS_INX-PLANT,
 TARGET_QTYX LIKE ORDER_ITEMS_INX-TARGET_QTY,
 ITM_NUMBER LIKE ORDER_ITEMS_IN-ITM_NUMBER,
 MATERIAL LIKE ORDER_ITEMS_IN-MATERIAL ,
 PARTN_ROLE LIKE ORDER_PARTNERS-PARTN_ROLE,
 PARTN_NUMB LIKE ORDER_PARTNERS-PARTN_NUMB,
 END OF TAB.
DATA: v_vbeln TYPE bapivbeln-vbeln.
selection-screen begin of block b1 with frame.
skip 3.
parameter:p_infile like rlgrap-filename obligatory.
skip 3.
selection-screen end of block b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_infile.
PERFORM value_help.
start-of-selection.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
 filename = p_infile
 FILETYPE = 'DAT'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
tables
 data_tab = tab.
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
**Validation for the Create SO screen
*AT SELECTION-SCREEN ON BLOCK na_create.
Loop at Tab.
i_header-doc_type = TAB-DOC_TYPE .
i_header-sales_org = TAB-SALES_ORG.
i_header-distr_chan = TAB-DISTR_CHAN .
i_header-division = TAB-DIVISION .
append i_header.
*endloop.
i_partner-partn_role = TAB-PARTN_ROLE .
i_partner-partn_numb = TAB-PARTN_NUMB.
APPEND i_partner.
i_details-material = TAB-MATERIAL .
APPEND i_details.
endloop.
*Bapi for Creating SO
 CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 SALESDOCUMENTIN = v_vbeln
 order_header_in = i_header
 ORDER_HEADER_INX =
 SENDER =
 BINARY_RELATIONSHIPTYPE =
 INT_NUMBER_ASSIGNMENT =
 BEHAVE_WHEN_ERROR =
 LOGIC_SWITCH =
 TESTRUN =
 CONVERT = ' '
 IMPORTING
 SALESDOCUMENT = v_vbeln
 tables
 RETURN = i_return1
 ORDER_ITEMS_IN = i_details
 ORDER_ITEMS_INX = ORDER_ITEMS_INX
 order_partners = i_partner .
 ORDER_SCHEDULES_IN =
 ORDER_SCHEDULES_INX =
 ORDER_CONDITIONS_IN =
 ORDER_CONDITIONS_INX =
 ORDER_CFGS_REF =
 ORDER_CFGS_INST =
 ORDER_CFGS_PART_OF =
 ORDER_CFGS_VALUE =
 ORDER_CFGS_BLOB =
 ORDER_CFGS_VK =
 ORDER_CFGS_REFINST =
 ORDER_CCARD =
 ORDER_TEXT =
 ORDER_KEYS =
 EXTENSIONIN =
 PARTNERADDRESSES =
IF NOT v_vbeln IS INITIAL.
*Bapi Commit Work
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT =
IMPORTING
return = i_return2
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
IMPORTING
RETURN =
ENDIF.
LOOP AT i_return1 . "INTO wa_return1.
WRITE:/ i_return1-message.
ENDLOOP.
FORM value_help .
CALL FUNCTION 'DSVAS_DOC_WS_FILENAME_GET_50'
 EXPORTING
 DEF_FILENAME = ' '
 DEF_PATH = ' '
 MASK = ',.,..'
 MODE = 'O'
 TITLE = ' '
 IMPORTING
 FILENAME = p_infile
 EXCEPTIONS
 INV_WINSYS = 1
 NO_BATCH = 2
 SELECTION_CANCEL = 3
 SELECTION_ERROR = 4
 OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
txt file data
order type salesorg distch divison materialno parter role
TA PB01 01 00 000000000000000852 WE
Partner no
8101000000

Hi Neerja,
you can reffer this sample code. It may not be complet soluation for your poblem,
but you will get some idea.
*& Report ZBAPI_SALESORDER_CREATE
*& Author : Karthik
REPORT ZBAPI_SALESORDER_CREATE.
data : ORDER_HEADER_IN like BAPISDHD1.
data : ORDER_ITEMS_IN like BAPISDITM occurs 0 with
header line.
data : RETURN like BAPIRET2 occurs 0 with header line.
data : ORDER_PARTNERS like BAPIPARNR occurs 0 with
header line.
DATA : ORDER_KEYS LIKE BAPISDKEY OCCURS 0 WITH HEADER
LINE.
data : ORDER_SCHEDULES_IN like BAPISCHDL occurs 0 with
header line.
data : BEGIN OF TAB OCCURS 0,
 SRNO(4),
 DOC_TYPE like ORDER_HEADER_IN-dOC_TYPE,
 SALES_ORG LIKE ORDER_HEADER_IN-SALES_ORG,
 DISTR_CHAN LIKE ORDER_HEADER_IN-DISTR_CHAN,
 DIVISION like ORDER_HEADER_IN-DIVISION,
 REQ_DATE_H(10),
 PURCH_DATE(10),
 PMNTTRMS LIKE ORDER_HEADER_IN-PMNTTRMS,
 PURCH_NO_C LIKE ORDER_HEADER_IN-PURCH_NO_C,
 ITM_NUMBER like BAPISDITM-ITM_NUMBER,
 CUST_MAT22 LIKE ORDER_ITEMS_IN-CUST_MAT22,
 PLANT LIKE ORDER_ITEMS_IN-PLANT,
 TARGET_QTY LIKE ORDER_ITEMS_IN-TARGET_QTY,
 PARTN_ROLE LIKE ORDER_PARTNERS-PARTN_ROLE,
 PARTN_NUMB LIKE ORDER_PARTNERS-PARTN_NUMB,
 END OF TAB.
data: itab1 like alsmex_tabline occurs 0 with header
line.
DATA: gd_currentrow type i.
data : PURCHASEORDER like ekko-ebeln.
Data: tot_rec type i, "Total Records
 gd_update type i, "Main Table Increement Counter
 gd_lines type i, "Success Table increement Counter
 w_textout like t100-text. "VARIABLE TO GET ERRORLOG
data : begin of it_success occurs 0,
 SALESDOCUMENT LIKE BAPIVBELN-VBELN, "PROJECT
 end of it_success.
data : begin of it_error occurs 0,
 srno(4),
 err_msg(73) TYPE c, "TO RETREIVE ERROR MESSAGES
 end of it_error.
data : srno(4).
DATA : SALESDOCUMENT LIKE BAPIVBELN-VBELN.
selection-screen begin of block b1 with frame.
skip 3.
parameter:p_infile like rlgrap-filename obligatory.
skip 3.
selection-screen end of block b1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_infile.
PERFORM value_help.
start-of-selection.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 filename = p_infile
 i_begin_col = '1'
 i_begin_row = '2' "Do not require
headings
 i_end_col = '22'
 i_end_row = '10000'
 TABLES
 intern = itab1
 EXCEPTIONS
 inconsistent_parameters = 1
 upload_ole = 2
 others = 3.
if sy-subrc <> 0.
 message e010(zz) with text-001. "Problem uploading
Excel Spreadsheet
endif.
*perform open_group.
sort itab1 by row col.
Get first row retrieved
read table itab1 index 1.
Set first row retrieved to current row
gd_currentrow = itab1-row.
loop at itab1.
Reset values for next row
 if itab1-row ne gd_currentrow.
 append tab .
 clear tab.
 gd_currentrow = itab1-row.
 endif.
 SHIFT ITAB1-VALUE LEFT DELETING LEADING SPACE.
 case itab1-col.
 when '0001'.
 TAB-SRNO = itab1-value.
 when '0002'.
 TAB-DOC_TYPE = itab1-value.
 when '0003'.
 TAB-SALES_ORG = itab1-value.
 when '0004'.
 TAB-DISTR_CHAN = itab1-value.
 when '0005'.
 TAB-DIVISION = itab1-value.
 when '0006'.
 TAB-REQ_DATE_H = itab1-value.
 when '0006'.
 TAB-PURCH_DATE = itab1-value.
 when '0007'.
 TAB-PMNTTRMS = itab1-value.
 when '0008'.
 TAB-PURCH_NO_C = itab1-value.
 when '0009'.
 TAB-ITM_NUMBER = itab1-value.
 when '0010'.
 TAB-CUST_MAT22 = itab1-value.
 when '0011'.
 TAB-PLANT = itab1-value.
 when '0012'.
 TAB-TARGET_QTY = itab1-value.
 when '0013'.
 TAB-PARTN_ROLE = itab1-value.
 when '0014'.
 TAB-PARTN_NUMB = itab1-value.
 endcase.
endloop.
append tab.
clear tab.
sort tab by SRNO.
LOOP AT TAB.
 concatenate tab-REQ_DATE_H+4(4)
tab-REQ_DATE_H2(2) tab-REQ_DATE_H0(2) into
tab-REQ_DATE_H.
 concatenate tab-PURCH_DATE+4(4)
tab-PURCH_DATE2(2) tab-PURCH_DATE0(2) into
tab-PURCH_DATE.
 SRNO = TAB-SRNO.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = tab-PARTN_NUMB
 IMPORTING
 OUTPUT = tab-PARTN_NUMB.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = tab-CUST_MAT22
 IMPORTING
 OUTPUT = tab-CUST_MAT22.
 IF TAB-SRNO = SRNO.
 ORDER_HEADER_IN-DOC_TYPE = TAB-DOC_TYPE.
 ORDER_HEADER_IN-SALES_ORG = TAB-SALES_ORG.
 ORDER_HEADER_IN-DISTR_CHAN = TAB-DISTR_CHAN.
 ORDER_HEADER_IN-REQ_DATE_H = TAB-REQ_DATE_H.
 ORDER_HEADER_IN-PURCH_DATE = TAB-PURCH_DATE.
 ORDER_HEADER_IN-PMNTTRMS = TAB-PMNTTRMS.
 ORDER_HEADER_IN-PURCH_NO_C = TAB-PURCH_NO_C.
 ORDER_HEADER_IN-DIVISION = tab-DIVISION.
 ORDER_ITEMS_IN-ITM_NUMBER = tab-ITM_NUMBER.
 ORDER_ITEMS_IN-material = TAB-CUST_MAT22.
 ORDER_ITEMS_IN-PLANT = TAB-PLANT.
 APPEND ORDER_ITEMS_IN.
 ORDER_PARTNERS-PARTN_ROLE = TAB-PARTN_ROLE.
 ORDER_PARTNERS-PARTN_NUMB = TAB-PARTN_NUMB.
 APPEND ORDER_PARTNERS.
 ORDER_SCHEDULES_IN-ITM_NUMBER = tab-ITM_NUMBER.
 ORDER_SCHEDULES_IN-REQ_QTY = tab-TARGET_QTY.
 append ORDER_SCHEDULES_IN.
 ENDIF.
 AT END OF SRNO.
 CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 SALESDOCUMENTIN =
 ORDER_HEADER_IN = ORDER_HEADER_IN
 ORDER_HEADER_INX =
 SENDER =
 BINARY_RELATIONSHIPTYPE =
 INT_NUMBER_ASSIGNMENT =
 BEHAVE_WHEN_ERROR =
 LOGIC_SWITCH =
 TESTRUN =
 CONVERT = ' '
 IMPORTING
 SALESDOCUMENT = SALESDOCUMENT
 TABLES
 RETURN = RETURN
 ORDER_ITEMS_IN = ORDER_ITEMS_IN
 ORDER_ITEMS_INX =
 ORDER_PARTNERS = ORDER_PARTNERS
 ORDER_SCHEDULES_IN = ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX =
 ORDER_CONDITIONS_IN =
 ORDER_CONDITIONS_INX =
 ORDER_CFGS_REF =
 ORDER_CFGS_INST =
 ORDER_CFGS_PART_OF =
 ORDER_CFGS_VALUE =
 ORDER_CFGS_BLOB =
 ORDER_CFGS_VK =
 ORDER_CFGS_REFINST =
 ORDER_CCARD =
 ORDER_TEXT =
 ORDER_KEYS = ORDER_KEYS
 EXTENSIONIN =
 PARTNERADDRESSES =
 IF SALESDOCUMENT <> SPACE.
 commit work.
 ADD 1 TO gd_update.
 it_success-SALESDOCUMENT = SALESDOCUMENT.
 append it_success.
 CLEAR :SALESDOCUMENT,ORDER_HEADER_IN.
 REFRESH : RETURN,ORDER_ITEMS_IN,ORDER_PARTNERS.
 ELSE.
 loop at return.
 it_error-SRNO = tab-SRNO.
 it_error-err_msg = return-MESSAGE .
 Append it_error.
 ENDLOOP.
 CLEAR :SALESDOCUMENT,ORDER_HEADER_IN.
 REFRESH : RETURN,ORDER_ITEMS_IN,ORDER_PARTNERS.
 ENDIF.
 endat.
endloop.
DESCRIBE TABLE it_success LINES gd_lines.
IF gd_lines GT 0.
 Display result report column headings
 PERFORM display_column_headings.
 Display result report
 PERFORM DISPLAY_SUCESS.
ENDIF.
IF SUCESS FAILS Display Error Report
DESCRIBE TABLE it_error LINES gd_lines.
IF gd_lines GT 0.
 PERFORM errorheadings.
 PERFORM errorreport.
ENDIF.
*& Form display_column_headings
 text
FORM display_column_headings.
WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.
SKIP.
WRITE:2 'The following records inserted
successfully:'(013).
WRITE:/ sy-uline(15).
FORMAT COLOR COL_HEADING.
WRITE:/ sy-vline,
 (10) 'Sales order'(004), sy-vline.
WRITE:/ sy-uline(15).
ENDFORM. "display_column_headings
*Subroutine to display SUCESS REPORT
FORM DISPLAY_SUCESS.
FORMAT COLOR COL_NORMAL.
LOOP AT it_success.
 WRITE:/ sy-vline,
 (10) it_success-SALESDOCUMENT, sy-vline.
 CLEAR it_success.
ENDLOOP.
WRITE:/ sy-uline(15).
REFRESH: it_success.
FORMAT COLOR COL_BACKGROUND.
ENDFORM. "
DISPLAY_REPORT
*& Form errorreport
 text
FORM errorreport.
LOOP AT it_error.
 WRITE:/ sy-vline,
 (10) it_error-SRNO, sy-vline,
 (40) it_error-err_msg, sy-vline.
ENDLOOP.
WRITE:/ sy-uline(104).
REFRESH: it_error.
endform. "errorreport
*& Form ERRORHEADINGS
 text
FORM ERRORHEADINGS.
SKIP.
WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.
SKIP.
WRITE:2 'The following records failed during
update:'(008).
WRITE:/ sy-uline(104).
FORMAT COLOR COL_HEADING.
WRITE:/ sy-vline,
 (10) 'ERROR.'(009), sy-vline.
WRITE:/ sy-uline(104).
FORMAT COLOR COL_NORMAL.
ENDFORM. "ERRORHEADINGS
**& Form value_help
 text
--> p1 text
<-- p2 text
FORM value_help .
CALL FUNCTION 'DSVAS_DOC_WS_FILENAME_GET_50'
 EXPORTING
 DEF_FILENAME = ' '
 DEF_PATH = ' '
 MASK = ',.,..'
 MODE = 'O'
 TITLE = ' '
 IMPORTING
 FILENAME = p_infile
 EXCEPTIONS
 INV_WINSYS = 1
 NO_BATCH = 2
 SELECTION_CANCEL = 3
 SELECTION_ERROR = 4
 OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform. "value_help
Regards,
Amit.

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.

Problem with Sourcing for multiple line items SRM 7.0

Dear All,
We are in SRM 7.0, extended classic scenerio,
For sourcing we have selected config "Sourcing is carried out for items without a Assigned source of supply" for all sytems and all product categories
Our requirement is Catalog items should not go to sourcing, Item with and without assigned source of supply both should go to sourcing and external requirements SC should go to sourcing.
We have done coding in BADI "DOC SAVE BADI" and "BBP_SRC_DETERMINE" method DETERMINE_SOURCING.
Now we create SC with line items only using Catalog it is working fine, SC not going to sorcing,
Create SCfor line items with assigned source of supply only it is working fine, SC going to sourcing,
and Create SCfor line items without assigned source of supply only it is working fine, SC going to sourcing,
But problem is with the combination of all items i.e. Catalog, with and w/o assigned source of supply in one SC
Assigned source of supply item is not appearing in Sourcing cockpit, and some time catalog items also available for sourcing.
Please help
Thanks in Advance
Vikas
Edited by: VIKAS CHINCHORE on Oct 4, 2011 11:53 AM
Any luck?

Hi
Please revisit your logic wriiten in this method
DETERMINE_SOURCING
Are you checking here sc has item or sc has supplier or not ( fixed supplier) in the logic? it must be item check.
As per sap standard , catalog item / fixed source of supply assigned will not venture to cockpit (Sourcing is carried out for items without a Assigned source of supply)

PO item with Multiple Goods receipt line items

Hi Experts,
When we create PO for specific vendor with one PO line item then at the time of Good receipt there are multiple GR line items. How to control those multiple GR line items as one GR item.
Appreciated your help
Regards
Krishna

Hi,
If you did GR from PO with underdelivery qty in line items, SAP recognize it as partial delivery.
Basically, in the standard system the underdelivery qty scenario is allowed, but not for overdelivery qty.
If you intended to force the system to allow one line item in PO with only one line item in GR, therefor you could create program checking with development team.
please check the link for your reference.
http://help.sap.com/saphelp_47x200/helpdata/en/a5/63344643a211d189410000e829fbbd/frameset.htm
regards,
rob

Is anyone else having an issue with the iPad not charging if you use it while it's plugged into a power source? Now that I'm on iOS 7, I either charge or use... Not both.

Is anyone else having an issue with the iPad not charging if you use it while it's plugged into a power source? Now that I'm on iOS 7, I either charge or use... Not both.

No problems here.
Edit...
My IOS-7 is on an iPod Touch.

163; There seems to be an issue with the template that the site is using as there is a code to replace the pricing.

163;
There seems to be an issue with the template that the site is using as there is a code to replace the pricing.
<script>
// Script to extract the currency and decimals from the price
var price = "{tag_saleprice}";
var priceWithoutCurrency = price.replace( /^\D+/g, '')
var decimals = priceWithoutCurrency.substring(priceWithoutCurrency.length - 2, priceWithoutCurrency.length);
var roundedPrice = priceWithoutCurrency.substring(0, priceWithoutCurrency.length - 3);
$('.image-with-price.big span').html(roundedPrice+''+decimals+'');

Here are the screenshots for what it's worth.
Not sure why I can't post them in the original post. 
Mod edit: See [https://bugzilla.mozilla.org/show_bug.cgi?id=718813 bug 718813]
'''Again, when I set my DNS server to automatically detect the servers both problems disappear and I have no issues at all.'''
IMO opendns is either doing this on purpose (unlikely) or they're under some sort of attack/being used to attack the specific torrent sites although I'm open to other explanations. I believe using the automatic setting for DNS is using my own ISP's DNS servers (which again, work fine... but still...)
I'd rather not use Google's public DNS servers as Google is to commercial these days and I think there's potential privacy issues.
'''Again I have changed the setting for DNS servers back and forth several times to duplicate/verify the issue(s)... and the issues only happen with the opendns servers.'''

Hello, I cannot show my video files on microsoft office program with macair book 11 inc notebook while using projector

I cannot show my video files on microsoft office program with macair book 11 inc notebook while using projector

When you next have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Multiple line items while clearing with f-44 abd f-32

Hello Team,
While clearing a vendor in f-44 or customer in f-32 system showing the double line items for bank account
in F-44
Vendor account DR 5000
to Bank account 4000(2000+2000)
to bank account 1000
in the above synario we have a open items 6000 (200020002000) but we are paying 5000 through check, system is showing bank account two line items instead of one line item.
it should show only one line item.
Would you please help me how to solve the issue
Regards,
Anantha.

Hello Ray,
I am very happy that some have taken tthe responsilibility of answering my query.
When i do the F-54, I am able to clear the vendor invoice against with the down payment. But if i go and see the WHT in respective GL account, they are still showing as " Open".
Please help me how to resolve it.
If this is not the correct way, kindly suggest me the right way.
Thanks for all your help
Regards,
Narasim

One pr for multiple materials with line items while running mrp

Hi SAP gurus,
              I am config the system for MRP as per my client requerement.
                 We use CBP for different RAW materialsfor example they having a 10 materials for planning,were,
         MRP type is VB,
          LOT size is FX,with Different Reorder points and fix order quantity for all materials,
         My client whant run MRP for all these materials in single time that means they whant multiple item at single levels,
        i soles these requirement with the help of Product Group(sop) and its working but when we running md02 for product group all materials have planed and they give different purchase requistion numbers for all these materials but my client Wants single purchase requistion with line items for all these materials.
     Pls give me the solution for that requirement.
thanks and Regards,
abhi

this is not the way SAPs MRP run works.
Where is the benefit for this?
the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

Generate 2 line items with posting keys in same table while using FM .

Dear Expert ,
For T-code f-65 ,I have to park a FI Document .i tried with PRELIMINARY_POSTING_FB01 for parked Document . But i am not successfully park the document .
with the help of F-65 the data Segregate between Tables VBSEGS and VBSEGD with respecting Posting key . but with this Fm entire entry is displaying in table VBSEGS .For example it generated two line items with posting keys '15' and '40' and these both are displayed in VBSEGS whereas posting key '15' has to be displayed in VBSEGD.
when i check this Document in FBV0 Error reflect " G/L Account 0012000 1001 Does not Exist ".
Here my code -
DATA:   XT_BKPF LIKE BKPF OCCURS 0 WITH HEADER LINE ,
        XT_BSEG LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEG1 LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEC LIKE BSEC OCCURS 0 WITH HEADER LINE ,
        XT_BSET LIKE BSET OCCURS 0 WITH HEADER LINE ,
        XT_BSEZ LIKE BSEZ OCCURS 0 WITH HEADER LINE ,
        XT_BKORM LIKE BKORM OCCURS 0 WITH HEADER LINE ,
        XT_THEAD LIKE THEAD OCCURS 0 WITH HEADER LINE ,
        XT_SPLTTAB LIKE ACSPLT OCCURS 0 WITH HEADER LINE ,
        XT_SPLTWT LIKE WITH_ITEMX OCCURS 0 WITH HEADER LINE .
DATA :    XTEXT_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XTEXT_ITEM_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XI_UF05A LIKE UF05A,
          XI_XCMPL TYPE XFELD VALUE 'X',
          XFS006_FB01 LIKE FS006 ,
          XI_TCODE LIKE T020-TCODE VALUE 'F-65',
          XI_PARGB LIKE RF05A-PARGB        ,
          XI_TCODE_INT TYPE TCODE           .
DATA P_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
XT_BKPF-BUKRS     =     'CP01'.
XT_BKPF-GJAHR     =     2011.
XT_BKPF-BLART     =     'DZ'.
XT_BKPF-BLDAT     =     SY-DATUM.
XT_BKPF-BUDAT     =     SY-DATUM.
XT_BKPF-MONAT     =     '06'.
XT_BKPF-CPUDT     =     SY-DATUM.
XT_BKPF-WWERT     = SY-DATUM.
XT_BKPF-USNAM     =     'ABAPER'.
XT_BKPF-TCODE     =     'F-65'.
APPEND XT_BKPF.
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '001'.
XT_BSEG-BSCHL = '40'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'S' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = '241000'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
Vendor line item - required even for header only - BSEG table
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '002'.
XT_BSEG-BSCHL = '15'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'H' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = 'PC04000001'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
CALL FUNCTION 'PRELIMINARY_POSTING_FB01'
   EXPORTING
     TEXT_UPDATE            = XTEXT_UPDATE
     TEXT_ITEM_UPDATE       = XTEXT_ITEM_UPDATE
I_UF05A                =
     I_XCMPL                = XI_XCMPL
FS006_FB01             =
      I_TCODE                = XI_TCODE
I_PARGB                =
I_TCODE_INT            =
IMPORTING
    XEPBBP                 = CHECK_A
    TABLES
      T_BKPF                 = XT_BKPF
      T_BSEG                 = XT_BSEG
      T_BSEC                 = XT_BSEC
      T_BSET                 = XT_BSET
      T_BSEZ                 = XT_BSEZ
T_BKORM                =
T_THEAD                =
T_SPLTTAB              =
T_SPLTWT               =
          EXCEPTIONS
            ERROR_MESSAGE = 1.
P_RETURN-ID         = SY-MSGID.
P_RETURN-TYPE       = SY-MSGTY.
P_RETURN-NUMBER     = SY-MSGNO.
APPEND P_RETURN.
     p_return-MESSAGE_V1 = XSYMSGV.
IF SY-SUBRC = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
ENDIF.
WRITE :/ sy-subrc , sy-MSGV1 .
Thanks ,
Ashish Gupta

Hi Raghuram,
I found a very important SAP Note 103051, details are below.
An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
Other terms
INVOIC, SAPLIEDI, M8047, M8, 321
Reason and Prerequisites
This is because of the program design.
Solution
There is no solution for IDOC_INPUT_INVOIC_MM.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
Hope this helps.
Reward if helpful.
Thanks

Issue with Sorting by Custom Attributes

In our custom SES query application, I am trying to implement sorting at the custom attribute level. I am having difficulty in understanding exactly how to set the options on doOracleOrganizedSearch() to achieve the desired result.
We have a table based content source and allow a user to search via custom search attribute. We are also going to allow them to sort by custom attribute.
For example, say we have a Project content source and one of the attributes is "Client Name". Users are going to be able to sort by client name (A-Z and Z-A). I have a prototype working but it only seems to work if I set topN to a very high number.
I want to bring back the first 10 documents sorted by Client Name A - Z and allowing paging to the next set of sorted results. My prototype works if I set topN to 1000 (more than the # of results) but does not work if I set it to 10 (# of results I want to display per page).
Below if my code. Note I am not setting the group attribute or the cluster list. Perhaps this is the issue?
Many thanks in advance!
OracleResultContainer results = service.doOracleOrganizedSearch
(this.m_query, // query
this.m_docsRequested, // topN
this.m_startIndex, // startIndex
new Integer(10), // docsRequested
this.m_dupRemoved, // dupRemoved
this.m_dupMarked, // dupMarked
this.m_searchDataGroup, // groups
this.m_queryLang, // queryLang
this.m_docLang, // docLang
this.m_returnCount, // returnCount
this.m_filterConnector, // filterConnector
filters, // filters
this.m_fetchAttributeNames, // fetchAttributeNames
null, // searchControls
null, // groupAttr
this.m_sortAttributes, // sortAttrList
null); // clusterList

Hi Nikola,
in 9.0.1 even if you rewrite the web interface you can't sort files by custom attributes setting a SortSpecification to a Folder. You can only sort by base attributes with getItems(). To get item sorted on custom attributes you must perform a search (a lot more codelines).
Regards, Alessandro

Adding new line item while save

Hi all,
use an implementation of BADI ME_PROCESS_REQ_CUST in the MM-Purchase-Requisition, method IF_EX_ME_PROCESS_REQ_CUST~POST while save.
based on the line items available(USER ENTERED) i have to add few more line items based on the account assignment category and quantity while save.
How to create new line items (copying the existing line item and change the quantity ) and save the requestion with the additional line items. I used this code. while calling the method CRETE_ITEM create based on the object REF_ITEM in the MY_STATE.
the REF_ITEM object is Initial . so while creation the empty object is created.
kindly help to give tips/details to handle.
Coding:
data: l_item_list TYPE MMPUR_REQUISITION_ITEMS,
l_item TYPE MMPUR_REQUISITION_ITEM,
l_item_akt TYPE mereq_item,
l_item_ref TYPE ref to IF_PURCHASE_REQUISITION_ITEM.
l_item_list = im_header->get_items().
loop at l_item_list into l_item.
l_item_akt = l_item-item->get_data( ).
IF l_item_akt-MENGE > 1 AND
       l_item_akt -KNTTP = 'A'.
      DO l_item_akt -MENGE TIMES.
         l_item-item= IM_HEADER->CREATE_ITEM( IM_ITEM = l_item-item).
        INSERT l_item INTO TABLE IT_ITEMS_list.
%%%%% here i checked useing    get data method i am not getting any data other than relesing procedure data.
I used SET_DATA method to set the data. even I am not getting data.
endloop.
(Debugging the code, I manage by doubleclicking while create Item method the fieldcontent of l_item (e.g ) to show the content of the class-attribute my_state. This works only if the field Interface in the Debugger is empty because then I see the attributes of the class. If the field Interface is filled with IF_PURCHASE_REQUISITION_ITEM, there arent any attributes shown.)
Thanks in advance for your kind help!!
Nicole

I searched sdn and found this not possible.

Create new line item while saving a new order

I have a requirement to create a new line item with different item category while creating an order.
i.e
if the item category is ICT1, then create a new line item like item 1 but with item category ICT2.
Also in the conditions tab, we need to update the condition type with different values for both existing and new item.
All this has to be in VA01 i.e on save.
I tried to append lines of structure XVBAP at SAVE_DOCUMENT _PREPARE by changing the item no and item caegory. This works fine. But, how can I get other table details like XKOMV(which stores pricing condition details) for the new item?
Please can you suggest any other exit/subroutine for this?
or any other alternative solutions

Hi,
Try to use this EXIT:
'EXIT_SAPMM06E_013' Update Customer's Own Data in Purchasing Document
The Badi and exit contains same parameter.
Thanks,
AMS

Issue in Printing of FBL1N ( Line Item Display)

Hi,
I have an issue with the printing of the report FBL1N...
When I execute the report with the Standard Layout "1SAP". The dispaly on the screen is correct. But when I tried print the output the display on the print out, excludes the Last Line item of the report & the Total's coloumn.
But when I try to Print the Formats Created by User's the Output is coming accurately
Can any one please inform me, what could be the issue, I tried printing of differnent printers, but the output is the same, also i tried adjusting the Rows & columns in Print Settings
Regards
Ash K

Hi,
When you print the report, try printing with some other printing layout like X_65_255.
I hope this will help you.
Regards,
Niraj

Issue with sorting of TO line item while using LM05 / LM07

Similar Messages

Maybe you are looking for