Transaction for Masive Asset Creation

Hi there !, Is there any way to create multiple assets at the same time from an excel file or a txt file ? So no need to create asset by asset using AS01 ?
thanks !

Hi,
SCAT is another tool where you can upload the master data. It uses the transaction recording procedure to upload data, somewhat similar to LSMW. But SCAT is even more simplified way.
You can record a SCAT with "AS91 - Legacy Master Upload" with amounts or you can record with "AS01 - New Master Creation" depending on your requirement.
Further for BDC you need the help of an ABAPer. But SCAT is meant for functional consultants only. You simply have to use te correct fields. Finding fields is also not difficult because SCAT provides them to you directly.
Regards,
Swapnil

Similar Messages

Recording transactions for an asset AS92

Hi,
I have an issue for the recording of transactions for takeovered asset.
First, I'm running a LSMW to take over all of my asset, after that I would like to run a second LSMW to update the asset with the different existing transactions : acquisition, retirement, transfers ...
I'm using (for the second LSMW) a batch input object 160, method 0001 with the program name : RAALTD01
Two structures are included on this program. As I previously read, I have to deal with the BALTB structure ... but what I'm doing with BALTD structure ?
an example :
asset number : 1000001 / 0000 (this asset is a takeovered asset), activ date the february, 1st 2009
company code : 0123
I would like to record this differents transactions :
acquisitions (code 100) of 1000 euros, the January, 1st 2009
acquisitions (code 100) of 1000 euros, the february, 1st 2009
retirements of 60, the february, 15th 2009
Where do I have to fill this data on the structure ? only BALTB ? or BALTB and BALTD ?
thanks in advance for your reply
Nicolas B

Hi,
thank you for your answer.
I did try the Batch recording. But the problem is to manage when you have more of one transaction on your asset.
example : record a transaction on your first line of the tab.
SAP will record that : RALT_DYNP_STRUC-BZDAT(1) with the index 1 corresponding to the first line.
But what happen you're trying to record a second transaction ?
Sap will trigger an error message mentionning RALT_DYNP_STRUC-BZDAT(1) is not an input field (because the first line is filled of your first transaction)
I thougt to manage this issue by filling the last line of the tab. But a second issue came : when you're pressing to the enter button, the amount disappaer ! then you have to fill it once again.
In fact, It's not a big deal. But how do you know the index, the position of your new line with the empty amount ?
I was very surprised that SAP doesn't propose the "insert line" button !!
NB

User Exit/BADI for AS01 ( Asset Creation )

Hi Xperts,
My requirement is during asset creation in AS01, after asset generated i want to send asset no, subno, asset creation date, int. order no to ztable.
Can anyone suggest user exit/BADI which suit this requirement.
I have gone through forum search, but not found suitable object.
Ram.

Hi Ram,
Check out below Badi and Enhancement
BADI
IHSA_LIST_EDITING
ENHANCEMRNT
EXIT_SAPLAAPM_002
EXIT_SAPLAIST_001
EXIT_SAPLAIST_002
EXIT_SAPLAIST_003
THANKS & REGARDS
G.Vendhan
Edited by: vendhan g on Jul 24, 2009 12:33 PM

Unable to use PIC01 transaction for Supersession chain creation

Dear All,
I am trying to create a supersession chain using PIC01 transaction. While entering the transaction, i am getting error as "Transaction Code PIC01 cannot be executed. You are trying to execute the transaction code &1, but it is in a deactivated package.
System Response
Execution is cancelled.
Procedure
Use transaction SFW5 to check whether all components required for the operation of your system are activated (switched on).
How should i resolve this. I checked in SFW5, but couldnt really know which package i should activate etc.
thanks in advance for your help.

Hello shyamsundarl
If you are using the DIMP solution only for the Supersession
functionality and not for the MPN, you would only have to activate
DIMP_SDUD Business Functions.
Please read note 849981 and discuss the issue with your SAP consultant.
Consider that settings of buisiness function sets (TA SFW5) are
irreversible... so please do the switch first on a dev system only,
and test carefully!
Enda.

LSMW for Asset Creation not creating Transaction

Hi,
I am using standard LSMW for creating Asset into the SAP system and passing transaction code as AS91.
Object: 0160
Method: 0001
Program Name: RAALTD01
Program Type: B
The asset is getting created, but even after passing the Transaction Data (Structure BALTB), with T-Code AS91, it is not creating the transaction record into Asset.
Any solution / work around for this?
Thanks & Regards,
Sandip kamdar

try with recording method, i had done this for same tcode and sucessfully completed the job.

User Exit / Badi / BTE for Asset creation A ?

Hi Experts,
I need User Exit / BADI / BTE for asset Creation.
After saving newly created Asset from As01 we need to send a mail to the person for whom the Asset is assigned.
i have tried all this.But no one is triggering after saving the As01 transaction.
Exit Name           Description
AAPM0001            Integration of asset accounting and plant maintenance
AFAR0003            External changeover method
AFAR0004            Determination of proportional values for retirement
AINT0004            Change amount posted for certain areas
AINT0005            Dummy for extended syntax check. Do not use.
AISA0001            Assign Inventory Number
AIST0001            Exchange number range in master data maintenance
AIST0002            Customer fields in asset master
AMSP0002            Determine relationship type for two company codes
TRAN0001            User exit for asset transfer
Please suggest if anybody worked on this.
regards,
Imran

Hi,
Check out the following posts pertaining to similar topic.
Change Asset Workflow
Asset Management WORKFLOW
Regards
Sreekanth

Any USER EXIT or BADI for modification in ME21N Asset Creation

Hi Guyz,
We have a requiremnt where we need to put some validaion/check in Asset Creation of ME21N,
Any possible BADIs or USER EXIT available for this modification.
Pease help.
Thanks
Jaif

Hi Jaif,
For BADIs please go to SE24 put cl_exithandler diplay it and put the break-point execute the transaction for which you want to find out badi you will get the badi name in exit name parameter.
Regards
Sagar

Accumulated depreciation transaction data upload for an asset

hi gurus,
i am uploading transaction data in the system. for the asset value i am using tcode f-90 but i am not getting the idea of how to upload an accumulated depreciation in for an asset
regards
sayeed

hi paul,
billions of thnx........ ABSO really works......
regards
sayeed
Edited by: sayeed bakhressa on Jan 28, 2009 12:28 PM

Delete the transferred values using the transaction for changing old assets

how to Delete the transferred values using the transaction for changing old assets.
i want delete the my asset.
Thank you
Anil

Dear Anil,
AS06 Delete Asset Record/Mark for Delet.
AS26 Mark group asset for deletion
Hope this will help.
Regards,
Naveen.

Creation Of Custom Transaction For RF enabled devices "mobile data entry"

Hello Everyone,
i need some information, or some material or some example's for creating custom transactions that will invoke the standard good issue transaction of sap from the handled device using the RF , so can anybody give some reference which will help me in creating custom transaction for a RF enabled handled device, which will invoke the standard sap goods issue transaction( mb1a) ,, there are some LM-transaction which do goods issue from the RF enabled handled device, but in my case i want to do goods issue using reservation as my input, so can anybody guide me or send some reference material matching to my problem, i would really appreciate it..
thanks in advance...
sapient2006

Hi Hussaini,
Here are the steps.
1> Customization needs to be completed in SPRO. Logistics Execution -> Mobile Data entry section. Also compare entries with LM01 for understanding.
2> In the 'Define menu management', you can create dynamic menus. For Menu or transaction type, if you enter "1", a menu appears; if you enter "2", a transaction appears. Custom transactions can be created and assigned here.
Once that is done, when you execute LM01 you will see your custom transactions come up. Make sure that these are created keeping in mind the RF device screen size and limitations.
Regards,
Anand.

How to test a new transaction type in Asset Accounting?

Hello everybody,
I need to explain how to test if the creation of a new transaction type in Asset Accounting was correct.
In other words, under what condition what should be the expected result.
The requirement was:
Create 2 new transaction types in asset accounting in order to book various business transactions:
- Create a new transaction type in asset accounting in order to book the credit memo.
- Create a new transaction type in asset accounting in order to book the scrapping cost.
And we make it throught AO73 transaction - Define Transaction Types for Acquisitions u2013 and OAYA transaction - Limit Transaction Types to Depreciation Areas u2013
Many thanks in advance,
Alvaro

Hi Alvaro,
I think best is you test a posting with the standard transaction typ delivered by SAP first. For example for credit memo in the aqcuisition year the standard tty is 105. If you post with this transaction type you then can check the document and you will see what line items are posted in which way.
To create your own transaction type:
You can check the customizing in the standard transaction type and then you could copy it to your own transaction type and give it your own name, and which you may then want to limit to certain depreciation areas via OAYA as you rightly pointed out.
For retirement by scrapping I would suggest the same: make a posting using the standard delivered transaction types and then check the document to see how the system posts. The make the required admustments in your own created transaction type copied from the standard transaction type.
I hope this helps,
Kind regards,
Brigitte

Asset Creation Event Error

Hi All
I have a requirement to start a workflow when an asset is created. I am using BUS1022. I have created and activated the linkage.
The entry in SWED exists for change doc: ANLA and the table ANLA
I have created a similar entry in SWEC for the event CREATED.
When i create an asset, the event does get triggered but there is an error., In SWEL it shows up as
Check FM with exception.
Receiver type :TS00001003
Message: Element FLAG_ANLAGE_BEARB is not available in the container
Check FM: AWFC_CHECK_ASSET_INCOMPLETE
Now I Have created the above mentioned element in my workflow and passed it the values in binding.
Where do i have to define this parameter? It is required in the parameters of the event---.
Thank you

Hi,
I am using other workflows like PR, PO, SO and too many WF templates, for those workflows also the event trace is not getting. But the workflows are getting triggered with out any problem.
Steps for event trace is SWELS for switch on the event trace and then executing the transaction (AS01) then after I am checking the event trace by using SWEL.
Can you pls advise the proper way for getting event trace, if I am not using the proper way.
Can any body explain the process for Asset creation.
Is there any equipment needs to be created before of after of Asset creation. I thougt, depends on this the CREATED event get triggers.
Thanks in adv.
Krish.

Asset Creation in PR and PO and MIGO as a single Line item with "N" qty

Hi All,
In Purchase requestion ME51N
Now we are creating "n" number of assets ( All are same item but "s.no" will vary) with "n" number of line item.
Instead of this I have to enhance to create only one line item( For same item) with "n" quantity.
for the ASSET account Assignment we have to create Asset(Temp no) for the each item/quantity(if the same item).
as well as if they are going to create a PO with ref to PR they have to see all the "n" number of asset no.
In MIGO creation for each asset we have to assign S.No and Asset Tag.
How enhance the functionality in PR,PO and MIGO as well as in Invoice.
Is it any User Exit/BADI is available for PR/POand MIGO to show all the "n" number of assets for a single line item.
Kindly help me to give details to proceed further.
Thanks in advance.
sharma

Hi Sharma,
What i understand from your question is, you want to create a single line item in PR and PO. But the qty would be > 1.
Each single qty would have its own asset number in account asssignment tab of item details of PR & PO.
This is what you are expecting...Right???????????????
Then this is possible with certain limitations.
While creating PR, enter only one item with more qty.
In item details section, in account assignment tab, on top left corner, there will be a button called Multiple account assignments.
Click on it, then it looks like a table, where you can enter more than one line. (each line will have its own asset no)
And choose option Distribute on qty basis for field Distribution.
So that you can enter 1 qty for each line. ( Ex: if you created one line item in the item level with 10 qty, you need to maintain 10 line here, each qith 1 qty and diff asset no).
The only limitation to this is, the GRN would be treated as non valueted. So when you make GRN there wwould not be any accounting doc. ( means no use of GR/IR clearing account as like normal for POs)
when you prepare MIRO, all the assets will be capitalised and vendor credited.
But in case if you receive partial invoice, then you have choose manually in MIRO. which asset is ot be capitalised.
After entering the PO number in MIRO, there will be one line will be appeared with full qty. in the same line, move till the end of line, there you will have one button called Account assignments.
Choose and go there, here you can choose which individual asset line to be considired.
This will resolve your issue.
Thanks,
Srinu
SRBORIGI_MULTIPLE ACCOUNT ASSIGNMENTS

While doing LSMW standard method for Customer master creation..

while doing LSMW standard method for Customer master creation.....
In 13th step I am getting this king of error
FB012 Session 1 : Special character for 'empty field' is /
FB007 Session 1 session name ZPROJ was opened
FB109 Trans. 1 : Transaction xd01 is not supported
FB016 ... Last header record ...
FB014 ... BKN00-STYPE 1
FB014 ... BKN00-TCODE xd01
FB014 ... BKN00-KUNNR
FB014 ... BKN00-BUKRS
FB014 ... BKN00-VKORG A1
FB014 ... BKN00-VTWEG 00
FB014 ... BKN00-SPART 0
FB014 ... BKN00-KTOKD
FB014 ... BKN00-KKBER BP01
FB013 ....Editing was terminated
Can anyone help how to solve this?

Hello TJK,
FB012 Session 1 : Special character for 'empty field' is /
This is the special function in LSMW, for empty field system will put / sign automatically, so you need not to worry about that.
FB007 Session 1 session name ZPROJ was opened It is opening session ZPROJ which is your project name/object name.
FB109 Trans. 1 : Transaction xd01 is not supported
Check out your field mapping and conversion rule for object.
FB013 ....Editing was terminated
It is not finding proper field mapping rule / file inputs so the sytem terminates the LSMW object.
Check your field mapping and conversion rule, check your source fields, save the file in tab delimited format.
Hope this helps.
Regards
Arif Mansuri

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
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
Eswar

Transaction for Masive Asset Creation

Similar Messages

Maybe you are looking for