Rejected Requisition - How do I edit line item?

Hi
I'm a bit of a noob when it comes to Purchase Requisition configuration, so I hope this will be an easy question for a config veteran to answer.
On our system, when a requisition line item has been refused/rejected, i.e. EBAN-BANPR = '08' (Release Refused), the requisition can't be changed. In ME52N, the only field that is available for editing is the header text.
Can this be changed? Can one attach a certain Field Selection to this refused status? I've had a trawl on the web, but can't seem to find an answer. So, any assistance would be greatly appreciated.
Thanks
Lyal

Hi Sanjay
Thanks for the reply. I have had a bit of a test, and I suppose that makes sense now. The requestor cancels the rejection, which then opens the line item fields for input. The relevant changes can then be made, and only when the user presses the save button does the RELEASESTEPCREATED event get triggered, which then starts the next stage of the workflow.
Thanks again!
Lyal

Similar Messages

How to delete a line item from the sales order

Hi all,
how to delete a line item from the sales order for which the production is already happened and it has been delivered. the production order status is DLV.
Regards
Kumar

Hi
U can do this in two ways one u can short close the order by entering Reason for rejection in VA02 at header level and if yr order is multiple line item order u can enter the reason for rejection in any of the line item which u don't want to deliver.
This is called short close ( as the qty is not delivered fully).
Thx.

How to delete the line item from a sales order

Hi all,
how to delete a line item from the sales order for which the production is already happened and it has been delivered. the production order status is DLV.
Regards
Kumar

Hi Kumar,
I think you can just delete it in the sales order directly, if you are using make-to-order scenario, then there will be special stock left for the sales order as the production has been goods receipt, you need to use MM transaction move the stock to unrestricted use stock. If you are using make-to-stock scenario, there should be no further problem. If you are using assembly order, please try to reject the sales order item to see if it could fullfill your requirement.
Regards,
Rachel

How to combine the line items of 2 Sales orders into 1 delivry

how to combine the line items of 2 Sales orders into 1 delivry
and their process, pre-requisites and tcode

The prerequisites are:
1) In the customer master sales area data, shipping tab, there is a field called Order combination. u must tick that.
2) for the two orders, the sold to party & ship to party must be same
3) both orders must have created from same plant & shipping points
4) the line items must have same loading grp.
5) the both orders sheduline line date must be same.
transaction code for the same is VL04.
enter the required data and select the order nos to be processed.
Do reward points if it is useful

How to change the line item storage location during the sales order creatio

How to change the line item storage location during the sales order creatio

Hi Kumar,
I think you can just delete it in the sales order directly, if you are using make-to-order scenario, then there will be special stock left for the sales order as the production has been goods receipt, you need to use MM transaction move the stock to unrestricted use stock. If you are using make-to-stock scenario, there should be no further problem. If you are using assembly order, please try to reject the sales order item to see if it could fullfill your requirement.
Regards,
Rachel

How to split a line item to 2 line item.

Hi all !
I have a request, help me please !
In system I have a invoice with 1 line item value 1000 USD.
Customer payment 600$. a incoming payment with value 600$ will post to system.
I want incoming payment and invoice will auto clear 600$ but system can't auto clearing because value is not Identical.
I want line item of invoice will split to 2 line item. Line item 1 value 600$ and line item 2 value 400$.
Line item 1 of invoice will auto clear with incoming payment and system will exist a invoice with 1 line item value 400$.
How to split a line item to 2 line item ? Have FM for split a line item to 2 line item in SAP ?
If you have other solution for this request, help me please !
Thanks !

Hi,
Have a look at Split line item - Sales Order
Regards

How to clear the line items once posted...

hello experts,
i m workiing on Enhancements in fi/co...i m not able to get the actual exit..
How to clear the line items once postings has been done...i.e. once v do postings in f-48 v assign an assignment with special GL a/c as 'A'(one line item generates)....and in Tr.code f-43 once the due as been settled i.e the payment as been done and same assignment has to be given(2nd line item generates) it has to clear with the transaction f.13.but it is not..there is a report program to check fbl1n(tr.code)...once it is cleared it is shown in cleared items else it is shown in open items.....can any one help me out...
i m providing the tech names of the fields...
same program for both the transactions-- sapmf05a screen no for f-48--304 and
f-43 ---110....
Assignment --- BSEG-ZUONR....AMOUNT ---(cluster table) BSEG-WRBTR....
SPECIAL GL A/C RF05A-UMSKZ(structure)
thanks n regards,
vamshi

The prerequisites are:
1) In the customer master sales area data, shipping tab, there is a field called Order combination. u must tick that.
2) for the two orders, the sold to party & ship to party must be same
3) both orders must have created from same plant & shipping points
4) the line items must have same loading grp.
5) the both orders sheduline line date must be same.
transaction code for the same is VL04.
enter the required data and select the order nos to be processed.
Do reward points if it is useful

How to check plan line items for plan cost at network activity level?

Dear all,
How to check plan line items for plan cost at network activity level? The plan cost is done in network activity in CJ20N.
I am not able to check using CJI4 or CJI9 report.
Kindly advise.
Thanks and regards,
Jessie

Hi Jess,
Have you checked the navigation part which is being displayed on left hand side of report S_ALR_87013565 and S_ALR_87013533.? There you have option to check transaction currency and object currency when you double click on it.
In case if it is not being displayed under navigation. Then you can bring them on from transaction code CJE2. For eg: Report group for S_ALR_87013533 is 12KST1C. Double click on it and it will open up to do changes in report layout and many more. There you also have options to bring on transaction currency too. Similarly, you can check for other report groups as well just by checking the report description.
But I am not sure if suits your requirements. Wait for other experts to comment on this.
Regards,
Amit

How to insert multiple line items in fv60 using bdc.

Hi all,
 How to insert multiple line items in fv60 using bdcs

hi
chk this
DATA : IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA : IT_MESSAGES LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : V_EBELP(30) , V_MENGE(30) , V_WERKS(30), V_EMATN(30) ,
V_PEINH(30).
DATA : FILE TYPE STRING, V_MSG(100) , V_IND(2) TYPE N , FLAG VALUE 'X'.
PARAMETERS: P_FILE(50) TYPE C DEFAULT 'C:\ME21_TEST'.
DATA : BEGIN OF ITAB OCCURS 0,
 IND(02),
 LIFNR_001(010),
data element: BSART
 BSART_002(004),
data element: BEDAT
data element: EKORG
 EKORG_004(004),
 EKGRP_006(003),
data element: LPEIN
 LPEIN_005(001),
data element: EMATNR
 EMATN_01_007(018),
data element: EWERK
 WERKS_01_008(004),
data element: EPEIN
 PEINH_01_009(006),
data element: EWERK
 MENGE_01_013(017),
data element: AUFEP
 EBELP_014(005),
data element: AUFEP
 END OF ITAB.
START-OF-SELECTION.
FILE = P_FILE.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME = FILE
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
 DATA_TAB = ITAB
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.
SORT ITAB BY IND.
START-OF-SELECTION.
LOOP AT ITAB.
REFRESH IT_MESSAGES.
V_IND = V_IND + 1.
AT NEW IND.
READ TABLE ITAB INDEX SY-TABIX.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0100'.
PERFORM BDC_FIELD USING 'EKKO-LIFNR'
 ITAB-LIFNR_001.
PERFORM BDC_FIELD USING 'RM06E-BSART'
 ITAB-BSART_002.
*perform bdc_field using 'RM06E-BEDAT'
 ITAB-BEDAT_003.
PERFORM BDC_FIELD USING 'EKKO-EKORG'
 ITAB-EKORG_004.
PERFORM BDC_FIELD USING 'RM06E-LPEIN'
 ITAB-LPEIN_005.
PERFORM BDC_FIELD USING 'EKKO-EKGRP'
 ITAB-EKGRP_006.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
ENDAT.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0120'.
CONCATENATE 'EKPO-EMATN(' V_IND ')' INTO V_EMATN.
PERFORM BDC_FIELD USING V_EMATN
 ITAB-EMATN_01_007.
CONCATENATE 'EKPO-WERKS(' V_IND ')' INTO V_WERKS.
PERFORM BDC_FIELD USING V_WERKS
 ITAB-WERKS_01_008.
CONCATENATE 'EKPO-PEINH(' V_IND ')' INTO V_PEINH.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0120'.
PERFORM BDC_FIELD USING V_PEINH
 ITAB-PEINH_01_009.
*CONCATENATE 'EKPO-MENGE(' V_IND ')' INTO V_MENGE.
*perform bdc_dynpro using 'SAPMM06E' '0120'.
*perform bdc_field using V_MENGE
 ITAB-MENGE_01_013.
*CONCATENATE 'EKPO-EBELP(' V_IND ')' INTO V_EBELP.
PERFORM BDC_DYNPRO USING 'SAPMM06E' '0120'.
PERFORM BDC_FIELD USING 'RM06E-EBELP'
 ITAB-EBELP_014.PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
AT END OF IND.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=BU'.
ENDAT.
CALL TRANSACTION 'ME21' USING IT_BDCDATA MODE 'A'
 UPDATE 'S'
 MESSAGES INTO IT_MESSAGES.
 LOOP AT IT_MESSAGES WHERE MSGTYP = 'E' OR MSGTYP = 'A'.
 IF FLAG = 'X'.
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 DEST = FILLER8
 GROUP = 'GAMY_FAILURE'
 HOLDDATE = FILLER8
 KEEP = 'X'
 USER = SY-UNAME
 RECORD = FILLER1
 PROG = SY-CPROG
 IMPORTING
 QID =
 EXCEPTIONS
 CLIENT_INVALID = 1
 DESTINATION_INVALID = 2
 GROUP_INVALID = 3
 GROUP_IS_LOCKED = 4
 HOLDDATE_INVALID = 5
 INTERNAL_ERROR = 6
 QUEUE_ERROR = 7
 RUNNING = 8
 SYSTEM_LOCK_ERROR = 9
 USER_INVALID = 10
 OTHERS = 11
 IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 CLEAR FLAG.
 ENDIF.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'ME21'
 POST_LOCAL = NOVBLOCAL
 PRINTING = NOPRINT
 SIMUBATCH = ' '
 CTUPARAMS = ' '
 TABLES
 DYNPROTAB = IT_BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7
 IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 ENDIF.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
 ID = IT_MESSAGES-MSGID
 LANG = 'EN'
 NO = IT_MESSAGES-MSGNR
 V1 = IT_MESSAGES-MSGV1
 V2 = IT_MESSAGES-MSGV2
 V3 = IT_MESSAGES-MSGV3
 V4 = IT_MESSAGES-MSGV4
IMPORTING
 MSG = V_MSG
EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2
 WRITE : / V_MSG.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
 ENDLOOP.
IF FLAG NE 'X'.
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDIF.
 Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.
ENDFORM.
 Insert field *
FORM BDC_FIELD USING FNAM FVAL.
 CLEAR IT_BDCDATA.
 IT_BDCDATA-FNAM = FNAM.
 IT_BDCDATA-FVAL = FVAL.
 APPEND IT_BDCDATA.

How to add new line item using BAPI BAPI_CONTRACT_CHANGE for contract-ME32K

HI Experts,
how to add new line item using BAPI: BAPI_CONTRACT_CHANGE for existing contract.
Requirement:
Already the contract having two line items using ME31K.
Custom program has to add new line items in existing contract.
Thanks,
Sendil

I got the solution:
We can do like this:
1. Get all details using details, BAPI_CONTRACT_GETDETAIL.
2. After getting results, append new line item. Then use your BAPI.
Check this posting program.. where this bapi is used, use the same coding technique.
IDOC_INPUT_PURCONTRACT_CHANGE

How to increase the line items against the std no of line items in MIGO

hi,
I have PO with more than 100 line items
During GR system is showing the error message as
Maximum number of items F1 reached
What is the standard no of line items in MIGO
And how to increase the line items
Is there any notes to apply
plz give sutable solution
K.Raghuram

Do you get message F5727 "Maximum number of items in FI reached"? reason is that in FI the posting line has a three-digit line item number (BSEG-BUZEI).
SAP's note 117708 provides a modification. I am pasting solution below.
Via the summarization you can post documents with more than 999 items in
FI.
The modification required for this is small, in addition you have to
change 2 tables. The modification is carried out in FI not in invoice
verification.
To activate document summarization in FI proceed as follows:
- The changes are described in Note 36353 and for the
modification in Note 77161. You may also have to apply Note
67640 so that the document summarization affects inventory
management.
An advice for the notes:
36353: Solution point 3: Field name WERKS
77161: Solution point 2: Maintain table TTYPV with Transaction
SE16
- this has the following effects; you can no longer clear the
GR/IR clearing account on purchase order item level (but only
on purchase order level) and you can only display the FI data
summarized (also see Note 36353)

How do I edit an item in my reading list in Safari version 7.0.2?

How do I edit an item in my reading list in Safari version 7.0.2?
MacBook Pro Late 2008, Running Mavericks OS 10.9.2.
Safari version 7.0.2.

Right or control the web address then click then click:
Open in new tab / Open in new window / Mark as unread / Remove Item / or Clear Items.

What is line item datas,how can u check line item in Infocube?

Hi friends,
what is line item datas,how can u check line item in Infocube?

hi konda,
line item data
i shall give u an example .
consider a super market bill,
the bill has 1.customer name 2. bill number 3. date of purchase
the above line will be header.
line item data are the items which u purchase.
item 1 pencil 2 rubber 3. sharpner 4. cryon 5. sketch pens
above are line item datas. for a particular set of header data u may have many line item datas.
reward points if helpful.
bye.

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.

How to restrict vendor line items to be picked to 6 in f110 payment run?

Hai
how we can allow F110 programme to generate a clearing document for every 6 line items.Means if a vendor has 15 open items which are due for payment at the time of Automatic Payment Run . The System should generate 3 clearing documents. Means the split up should be 663. Means for the first 6 open items (1-6) one clearing document. For next 6 Open items (7-12) and for the last 3 Open Items(13-15) , One clearing Document to be generated.
Kindly Advice me. Surely Iam going to reward the ponits.
Thanks In Advance, Have A Great Day
Akash Narayana

1)block all doc's where count > 6 (per vendor) and do f110
2)unlock and repeat 1)
.. until all doc's are paid
A.
Message was edited by:
Andreas Mann

Rejected Requisition - How do I edit line item?

Similar Messages

Maybe you are looking for