Formule for tot processed doc
How do I need to create a formula in Crystal Reports (CR) to get the TotForm HR
Calculation to be performed is Totformhr= total processed*3600/timetaken
Kindly help me by guiding steps need to be taken to get this formula in crystal reports.How many variables need to be created.How to do calc
Form_type TotalProcessed Timetaken TotForm HR
HH:MM:SS
AAAA 15 0:00:46 1173.91
BBBB 1 0:00:12 300.00
CCCC 169 0:18:26 550.09
185 0:19:24 572.16
Thanks
Swathi
Hi Swathi
You will have to normalize all the fields in a common type.
Say for example all the values need to be converted in hours or minutes or seconds and then do all the calculations.
Extract Hours part:
numberVar hr;
numberVar final_hr;
final_hr:= hour(Desired Field}) + hr;
Extract Minutes Part:
numberVar m;
numberVar final_m;
final_m:=Minute ({@Formula 1}) +m;
Extract Seconds Part
numberVar s;
numberVar final_s;
final_s:=Second (Desired field) +s;
Now we can add the hour part minute part and seconds part for each field and then perform the desired calculation.
To represent the final value back into hh:mm:ss format use this formula:
TimeSerial((@formula1),(@Formula 2),(@Formula 3))
where,
@formula1 : is the total hours part
@formula2 : is the total minutes part
@formula3 : is the total seconds part
I think this would provide a basic idea to you and you will need to play around a bit to get to the exact results.
Let us know if there is something more we can share !!
Similar Messages
-
Crystal Reports VS 2008 "The request could not be submitted for background processing"
Hi,
I am going to try to explain this issue the best I can. Please let me know if you need any other information or have any ideas as I have exhausted my resources. We have an ASP.NET application that has highly formatted crystal reports in them that the users can export as PDFs. All reports export without a problem when the application is run off of our desktops. The reports use a sql server authenticated user, executing stored procedures, and each subreport is linked by the main parameter. We are using Visual Studio 2008 version 3.5 SP1 with Crystal Reports Basic for Visual Studio 2008 on Windows 7 Enterprise SP1. We have designed the reports in Crystal Reports XI Release 2 (11.5.12.1838) and imported them into the ASP.NET application. When trying to export the reports as PDFs from the development or production servers, we get the error message below for some, not all, reports:
System.Runtime.InteropServices.COMException (0x800002AD): Error in File C:\Windows\TEMP\KeyAccountProfile {9FA5C095-77A2-425D-AC6B-8BB66B435336}.rpt: The request could not be submitted for background processing. at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext) at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
We have cleared the temp directory on the servers before exporting and are still receiving the error. We have installed Crystal Reports Basic Runtime for Visual Studio (10.5.2.0) on both servers. I have identified the underlying issue to one stored procedure/subreport that is causing the report to fail. The weird thing is, when we change the connection to point to development, the stored procedure/subreport runs fine for the report that generates an error when run from production, and the data is the exact same. I have tried rebuilding the subreport but the error still appears even though it runs fine for other reports.
I have been through the document below, and othe similar issues in the forums, but still have not found a resolution. I was trying to use the "modules" application put since this is an ASP.NET application I am unsure of which executable I should be looking at.
http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/50a6f5e8-8164-2b10-7ca4-b5089df76b33?QuickLink=index&overridelayout=true&36837934524320
Thanks in advance for your assistance,
Brad Hood
06-26-14
OK.. I did some more investigating on this today. I have found out when I move the sub report that generates the error under another sub report, the sub report in question runs without issue. But when I try and move the sub report that produces the error above any other sub report, the error still generates. Can this get any weirder.... FYI.. there is a total of ten sub reports on this report.Hi Brad
I'm not sure that Modules would show us anything in this case, so let's try a few other things:
1) Make sure you are using SP 1 for Crystal Reports Basic Runtime for Visual Studio:
Crystal Reports for VS 2005 and VS 2008 Updates & Runtime Downloads
2) Seeing as this works on dev, this may be some db inconsistency so enabling the report option "Verify on 1st Print" will be a good idea.
3) Double check the database client and make sure the same client is used on dev and deployed systems. Actually I take back my Modules negative as this is where it may prove useful. Once you have the Modules logs, look at who is loading the crpe32.dll, then look at that process and see the client dlls.
4) Check the printer driver; see if there are any updates. Try a different printer driver.
Ten subreports is not too bad, though not that good either as you are loading the report engine with at minimum 11 simultaneous reports (each subreport is considered to be a report). If a subreport is in a details section and the details section returns a 100 records, you are running 100 + 1 reports. This may lead to memory issues, which may lead to the error.
If I was a betting man, I'd put most of my money on the printer driver (based on your last addition to your post). What ever money I had left would go to some database issue (be it actual data or client related).
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter -
Email Alert for Process Chain for ABAP Process Type
Hi BW Experts,
I created a process chain based on ABAP Process Type ( for Broadcasting rsrd_broadcast_starter). I want to add alert message for each ABAP process if it is failed. But I cant see any option showing Successfull or Error or Always when I select create message option on the process type. How ever I can see for other process chain which is loading data (Process Type is Info Package ) from SAP into BW.
Please some one tell me why it is not showing alert message for ABAP Process Type.
Thanks
Ganesh Reddy.
Edited by: Ganesh Reddy on Jul 13, 2009 10:16 PMI dont have the exact answer for your question, But as a work around i can suggest you that.
If these ABAP programs are included in a chain and this local chain is a part of meta chain then you can create a message on the local chain.By right clicking on the local chain >Create Message>Success
--->Failure
>Always
Hope this resolves the problem tempervorly.I will get back to you once i have
Or the permanent solution is
Its big and also easy method to perform, by this you will be able to get all the options for a ABAP Program also.If you have any questions please let me know.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/creating%20an%20abap%20process%20type%20for%20process%20chains%20in%20bi.pdf -
Error: The request could not be submitted for background processing
I'm getting an intermittent error in our custom reporting application using Crystal Reports Server XI R2 w/ SP1:
Error in File C:\WINDOWS\TEMP\{F6D30537-956A-458C-96D0-84ECB520D688}.rpt: The request could not be submitted for background processing.
I'm using the Report Application Server XI Release 2 .NET SDK. This is the code that produces the exception (The export type is pdf):
ByteArray ba = this.reportClientDocument.PrintOutputController.Export(ConvertExportReportTypeToCrystalReportExportType(),0);
The error is also logged by Business Objects in the crystalras log file:
ErrorLog 2007 12 3 12:24:56.531 6624 4872 (\servers\ras\dtsagent\reporthandler.cpp:11592): CReportHandler::buildReportViewerError: CSResultException thrown. ErrorSrc:"CRPE" FileName:"\servers\ras\dtsagent\reporthandler.cpp" LineNum:11588 ErrorCode:685 ErrorMsg:" Error in File C:\WINDOWS\TEMP\{F6D30537-956A-458C-96D0-84ECB520D688}.rpt:
The request could not be submitted for background processing." DetailedErrorMsg:""
This has been happening regularly about once a week, at which point the RAS fails and no more reports can be run until the CMS and RAS servers have been restarted.
Has anyone else had this problem, or have any ideas?
ThanksIt was not a bug (not in all cases anyhow), but it is one of those error message that might as well say; something went wrong. I wrote an article on the most likely cases for the error and the article can be downloaded from here;
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50a6f5e8-8164-2b10-7ca4-b5089df76b33
See if the above article will help you out. Please note that having the latest SP / FP is step one. The downloads page is here;
http://service.sap.com/sap/bc/bsp/spn/bobj_download/main.htm
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup -
Delete messages stuck in status 12, Recorded for Outbound Processing
I am on a PI 7.10 SP8 system. I have 59,000 XML messages showing in status 12 ( Recorded for Outbound Processing) that I would like to just delete or cancel. These have accumulated over several days of testing interfaces. If I have to allow them to be processed, that would also work but is not needed. I have read about 6 different forum threads and tried several things but nothing has worked yet. <br>
The messages can not be cancelled from SXMB_MONI. <br>
The queues are no longer showing in SMQ2. <br>
I have tried restarting and re-registering the queues. <br>
I've tried RSXMB_RESTART_MESSAGES and RSXMB_CANCEL_MESSAGES. <br>
SWPR & SWPC show nothing to restart. <br>
Any ideas on something else to try? <br>Hi,
You can try to delete or archive mesages. use following links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
Delete Messages SXMB_MONI
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Too many questions on Archive/Delete messages.
Inder -
Could not support request for background processing
Hello,
We have a .NET 1.x application with CrystalReportViewer control.
The application is running on a windows terminal server with approximatively 5 users using the applications and 10-20 logged on doing other stuff.
When the user tries to preview the report using the CrystalReportViewer object , the following exception is "sometimes" thrown
[translated from dutch]
CrystalDecisions.CrystalReports.Engine.InternalException:
error in file C:\Users\*username*\AppData\Local\Temp\35\{B8D10435-A104-4422-A220-6DB483DFC285}.rpt:
The request could not be submitted for background processing. ---> System.Runtime.InteropServices.COMException (0x800002AD)
The application then terminates and if the user restarts the application attempts to reload the report, it usually loads with no problem .
It can not be intentionality reproduced but it does happen frequently.
I have been Googling for this problem , but havn't found any solution.
On this website however a link is provided to a BO KB article with a possible solution:
http://aspadvice.com/blogs/rjdudley/archive/2005/10/26/13443.aspx
However, the article appears to require a login, my SAP CR account i used to register on these forums does not to work.
What can we do to determine the exact cause of this problem, or are there any known solution for this problem ??
If you need any more information please do ask.
also,
We have a licence for CR 11 and so does our client, what steps would we need to undertake to get professional /payed support from SAP crystal reports for techinal issues like this, is there a way to open a support ticket ?
Thank you very much for your time, any help is appreciated !
WillemHello:
First I have to apologize for the troubles with CR 11.5 - not sure why that would be, but your frustration is understood. Perhaps sometime in the future we can look at this in another thread (e.g.; it should just work...).
Anyhow, there is really no compeling reason for you to go to CR 11.5 (there are reasons (see below), but 11.0 is fine with framework 1.1).
So to start off. Version 11.0.0.895 will need to be updated to SP4. See this|http://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReports2008%28and9.1%2CXIR1%2CXIR2%29-VersionandDownloadinformationforServicePacks] wiki. As you can see in the wiki, the latest version of CR 11.0 is updated to SP 4 with a version of 11.0.9500.x. Before we even start to look at this, you will have to get to SP4.
Re. preference for CR 11.5. If the issue is not resolved with CR 11 Service Packed to SP 4, all we have left is; going to CR 11.5 - with the latest SP (SP6) as that is the version I would be testing with. Note that CR 11 is completely out of support now, CR 11.5 is out of patch support (e.g.; no fixes) and any support terminates in June of this year.
And we have not even started to work the issue. Re-reading your initial post, I am starting to suspect that loading may be the root of the issue here. I'd recommend having a peek at the following:
http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/d08468e2-a81d-2b10-faa9-9837f58ee1c2
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7025839b-00d4-2b10-33b4-cf0aa9e08412
The following article specifies CR 2008, but most if not all the points will apply to CR 11.0 also:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7025839b-00d4-2b10-33b4-cf0aa9e08412
The below will also be good to be aware of:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40bccdfd-88a6-2b10-1da1-c47a54b625a7
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0070692-01a8-2a10-4797-ff0f5f73e1e1
The following articles were written by me and may also apply:
[Crystal Reports Maximum Report Processing Jobs Limit|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/f053713e-3e3d-2c10-2a81-f79259e54023]
[Improving Crystal Reports Performance in Visual Studio .NET Applications|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8029cc96-6ff3-2b10-47a2-b30ea790ea5b].
I realize I've thrown a lot of info in here, but all of it may apply. In a way I feel like we've ended up across the river without crossing the bridge first, but let's see what comes out of all of this (teleporting worked for Captain Kirk ).
- Ludek
Edited by: Ludek Uher on Mar 10, 2011 7:25 AM -
Fox formula for actual/plan data - Planning function
Hello,
I am working on the following scenarios for developing a planning functions for a monthly forecast.
It is rolling montly forcast where user starts the planning in Jan and he has to show the actaul value for the month of Jan and blank values for the remaining 11 months of the year and then the user post his new forecast values for the remain 11 of the year(to replace initial balnk values) so that the data will be saved to real time cube with version v108
In Feb, Jan & Feb months has to show the act values and remaining 10 months has to show last month forecast data. The the user may revise the forecast for the 10 months and then we have to write the data to the real time cube with version v208
In Mar, Jan, Feb and Mar has to show the actual values and the reamining 9 months has to show the last month forecast and then users may revise the forecast data and then i have to write back to the cube with version v308.
I want to automate this process for all the months and all years without manual intervention. So, i decideed to write a fox formula for this scenario with following draft code.
I will get the fy period & year as a variable values and then take the system date into the variable
for each fy period
if the fy perio <= sys date.
{version, infoprovider,value type,amount} = {0,act cube, 10, 0amount)
else
{version, infoprovider,value type,amount} = {result,plan cube, 20, 0amount)
endif.
result will be calculated on the separe routine and populated here
case (fy per)
when 01.
concatenate v1 with fy+2(2) into y
result = v1+y
when 02.
concatenate v2 with fy+2(2) into y
result = v2+y
when 03.
concatenate v3 with fy+2(2) into y
result = v3+y
when 04.
concatenate v4 with fy+2(2) into y
result = v4+y
when 05.
concatenate v5 with fy+2(2) into y
result = v5+y
when 06.
concatenate v6 with fy+2(2) into y
result = v6+y
when 07.
concatenate v7 with fy+2(2) into y
result = v7+y
etc...for all months
So, can you please let me know the best way to implement this (either by fox formuls or exits)...your inputs are really appreciated
Thanks,
Srini
Edited by: srini on Mar 28, 2008 12:05 PMHi Srini,
If I 've understood u r problem clearly ,You have to write two Fox Functions and you can call exit variable in both to check the system date.
I think first you should create exit varriable which would return the system date,use the same variable in data slice to lock the data till current period.
After that create one fox restricted with any one version where you can copy the data for planning .for example:-
1)First Fox:-
DATA TIM_FISCPER TYPE 0FISCPER.
TIM_REF_FISCPER = VARV(ZEXIT_FPER).
Get the last month
version using modlue or any another logic .(v108)
FOREACH TIM_FISCPER.
IF TIM_FISCPER <= TIM_REF_FISCPER.
{0amount,version(001) ,tim_fiscper} = {0amount,version(000) ,tim_fiscper}.
else.
{0amount,version(001) ,tim_fiscper} = {0amount,version(v108) ,tim_fiscper}.
endfor.
Its just n example use the granularity according to the requirement.
2)Second fox would save the changed plan data:-
DATA TIM_FISCPER TYPE 0FISCPER.
TIM_REF_FISCPER = VARV(ZEXIT_FPER).
Get the last month
version using modlue or any another logic .(v208)
FOREACH TIM_FISCPER.
IF TIM_FISCPER > TIM_REF_FISCPER.
{0amount,version(v208) ,tim_fiscper} = {0amount,version(001) ,tim_fiscper}.
endfor.
Here ZEXIT_FPER is an exit variable created using cmod and populated with system date.
Hope it will helpful for u.
Rgds,
Indu -
Best practices or design framework for designing processes in OSB(11g)
Hi all,
We have been working in oracle 10g, now in the new project we are going to use Soa suite 11g.For 10g we designed our services very similar to AIA framework. But in 11g since OSB is introduced we are not able to exactly fit the AIA framework here because OSB has a structure different than ESB.
Can anybody suggest best practices or some design framework for designing processes in OSB or 11g SOA Suite ?http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/04_osb.htm
http://www.oracle.com/technology/products/integration/service-bus/index.html
Regards,
Anuj -
Result Recording for In Process Inspection
At the time of taking Usage Decision for In Process Inspection, system gives warning message if Results have not been recorded. Can this Warning message be changed to Error message so that user could not able to take UD without recording the results.
Thanks in advance
SriniDear Srini
1)Use status profile for restricting the user to do UD without doing RR. use this link for doing it
Link: [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20fbc091-ea3a-2b10-f0a3-877ffbf36436]
2) you can use this auth object for doing the same restriction - Q_INSP_FIN
Link: [Re: Preventing UD without results recording]
Regards
Gajesh -
Now to define new formulas for pricing?
can any one please tell me a business scenario where one needs to define a new pricing formula, and how can one can do that in the system?
points will be rewarded immediately.
thanks
PRHi,
As our friends suggested you can create new formulas for pricing with the Transaction code VOFM.
Process is use VOFM(Transaction code)------>in top menu you can see Formulas, select appropriate option in Formulas lke.. Condition base value, Condition Value etc.,
Please go through detail information:-
Formulas are represented as FORM routines. They are used in pricing and influence the determination of prices according to predefined rules. You can specify them in pricing control. The following groups of formulas exist:
Scale base value
The scale base value includes FORM routines which determine the scale base value according to criteria that are not defined in the standard system. You enter the scale base value in the Scale formula field. A formula for the scale base value can define, for example, that partial quantities are taken into account.
Condition base value
Formulas for the condition base value take into account criteria not defined in the standard system. You enter them in the Alternative formula for condition base value field in the pricing procedure. A formula for the condition base value can define, for example, that the condition determination is based on net value or volume.
Condition value
Formulas for determining of the condition value include routines which determine the condition value according to criteria not defined in the standard system. You enter the formulas for the determination of the condition value in the Condition formula for alternative calculation type field in the pricing procedure. A formula for the condition value can define, for example, that the system determines the best price for the customer.
Structure of group key
Using this menu entry, you can edit routines that determine the base value for the scale value if group conditions are used in pricing. The system then calculates the base for the scale value from more than one document item. You can enter the routines in the Group condition routine field on the screen for defining condition types. A routine for the determination of the scale valuecan define, for example, that only a particular condition type is taken into acount.
Rounding rules
Using this entry, you can create and edit FORM routines that carry out a particular type of rounding in the condition record during a price change. A rounding rule could round a price that was increased by 1% to the last two places behind the decimal point, for example.
Procedure
To define your own formulas, proceed as follows:
1. First check whether you can use the formulas delivered with the standard system.
2. Either overwrite an existing formula or select a group number from the number range reserved for customer modifications (600-699) and enter the corresponding description.
3. Program the formula in the editor.
4. Activate the formula.
5. Enter a long text that describes the meaning of the formula in more detail.
6. Enter an application if you want to use the formula in a particular application area only (pricing, for example).
7. Enter the formula in the appropriate place of the control
NOTE:- to create new routine get Access key from Basis.
I hope it will help you to define formulas for pricing.
Regards,
Venkat -
User Exits for Inbound Process
hi all
can any one please give some example user exits in inbound process and explain the omportance of user exits
Thank you,
Swapnahi
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
Types of User exits
1. Menu Exits
2.Function exits
3.Table exits
4.Screen exits
5.Keyword exits
6.Field exits.
also refer to the links below.. can get more info on user exits
list of user exits
http://www.planetsap.com/userexit_main_page.htm
can also get the list of user exits thru..
Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
User Exits Notes:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
below are some of the useful invound and outbound userexits
<b>IDoc Inbound User Exits</b>
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
<b>IDoc Outbound User Exits</b>
72. ACCONF
Confirmation of IDoc processing from the application
ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
General IDoc User Exits
ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
===
User exits for Pricing.
1.USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
2.USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
3.USEREXIT_FIELD_MODIFICATION
4.USEREXIT_FIELD_MODIFIC_KZWI
5.USEREXIT_FIELD_MODIFIC_KOPF
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
====
Reward if USeful
Thanx & regards
Naren.. -
hi, i know about bdump and udump, but where do the logs for network processes go? and what exactly are oracles network processes?
thhanksIt should be in $ORACLE_HOME/network/logs
Read this doc
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/architecture.htm#sthref484 -
Std. WF/Bo for consignment process in Sales?
Hi Friends,
Is there any std. WF/Bo for consignment process in Sales?. I will definitly award points for any useful hits.
Thanks
NashIt should be the same BUS2032, it's basically the doc type which differs.
Regards, IA -
BR100 Document for Oracle Process Manufacturing (OPM)
Hi,
Can anybody please send me sample BR-100 document for Oracle Process manufacturing for Steel / Coal slag processing industry??
Thanks in advance.
With Regards,
Vishal Gujar
Edited by: 956843 on Dec 14, 2012 12:42 PM11g is not release yet for SOA Suite. The latest version is 10.1.3.4.
here is some docs to get you started
http://www.oracle.com/technology/products/ias/bpel/htdocs/dev_support.html
cheers
James -
Steps for Creating Process chain!
Hi All,
I want to create process chain which can schedule IP and run the concern job to fill infocubes/ODS?Can someone please guide me stepwise how to proceed.Some sort of doc will eb appreciated.Hi,
You can either create a process chain directly in the process chain maintenance screen, or by using a maintenance dialog for a process
Creating a Process Chain Directly in the Process Chain Maintenance Screen
In the BW Administrator Workbench
1. Choose the Process Chain Maintenance icon from the AWB toolbar.
2. Choose Create.
3. Enter the technical name and a description of the chain, and confirm your entry.
4. Create a variant for a start process.
On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
If you choose to schedule the chain directly, enter the start date value for a chain under Change Selections and save your entries.
Save your entries, go back to the previous screen and confirm your entries in the Add Start Process dialog box.
The Plan View of the process chain maintenance screen appears.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
5. Use Drag&Drop or double-click to add the relevant processes to your process chain.
Choose Process Types to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert a process into the chain that is linked to additional processes by default, the respective process variants are generated and automatically inserted into the process chain. These variants are suggestions and can be changed, replaced or removed from the chain as required. Variant maintenance is called when the change run performs automatic insert.
a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c. Save your entries, go back to the previous screen and confirm your entries in the Add Start Process dialog box.
The Plan View of the process chain maintenance screen appears.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes by default, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain as required. Variant maintenance is called when the change run performs automatic insert.
Choose Process Types to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
When you add a process, you need to select a process variant or create a new variant. For collection processes, the system uniquely determines the variants.
Various functions for editing the process are available from the context menu
Maintain variants With the exception of the variants in the collection processes OR and EXOR, you can use this function to change all process variants.
Exchange variants
You can exchange the variants for an existing variant or a variant that is to be created.
You can use this function to link a process to a successor process. You can choose from the processes that are not yet linked to the current process. They are grouped according to process type in submenus.
Display scheduled jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
After at least one process chain run, you can display all of the scheduled jobs for a specific process and all of the jobs with which this process was run. The Job Overview appears and you can call the relevant job log.
Create message
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. To do this, using the context menu for a process, create another process variant of type Send Message.
2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. A dialog box appears, in which you can select an existing process variant or create a new one.
4. If you create a new process variant, edit the document that is going to be sent and maintain a list of recipients.
5. Save your process variant and go back.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log are also sent.
Only use this function to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process in the debugger by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove process
You use this function to remove a process from a process chain.
Manage data target
You use this function to call the data target administration for the following types of process variants:
Construct index
Delete index
Construct database statistics
Roll up filled aggregates
Compress InfoCube
Activate DataStore object data
7. Hold down the left mouse button to connect the processes with events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link. To do this, select the link and right-click with the mouse.
8. If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully, or whether you want the event to be triggered independently of the outcome of the process that precedes it. If the process that triggers the event has more than one option, choose the option after which the successor process is to be run
9. Assign a display component to the process chain using Attributes
10. Maintain additional process chain attributes if necessary.
11. Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
During the check, the system calculates the number of parallel processes according to the structure of the chain . The result is compared with the number of background processes on the chosen server (or the total of all available servers if no server is specified in the attributes of the process chain). If the number of parallel processes is greater than the number of available background processes, the system highlights every level of the process chain where the number of processes is too high. The system produces a warning for these levels.
12. Save your process chain if it does not contain any errors.
You can activate and schedule your process chain. After scheduling, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after scheduling. In the Log View, you can display the reports for the chain runs.
If ie helps assign points
Maybe you are looking for
-
Can I get a refund from In-App purchases?
My brother stole my IPod and spent £30 on two worthless games. Is it possible to get a in-app refund to get my money back?
-
My Classic IPod had been working perfectly with Windows Vista OS and on a dock. I left it unattended for 10 days, recharged it and tried to play music on the dock. All that shows on the screen is the Apple Logo and I am unable to restart or update th
-
If I delete my icloud account so that I can get one that matches my apple id and email and password that I updated due to a new email address, will I lose my contacts and pics and calendars on phone that were synched to icloud. It keeps warning me w
-
Refresh Textboxes in CS5.5 from CS3
Hello, in our company we had an big update a few days ago from cs3 to cs5.5. We use basically Illustrator in 95% of our filles. Now we've got problems with the textboxes and the text from our files before the update. They are all formed in Illustrato
-
Cannot log onto UME and Netweaver Admin pages
Hello, From the main WAS page (http://<servername>:5000) I am trying to log onto the User Management page. I cannot log on with ANY account regardless of whether an administrator or not. I get no error message, the page refreshes. The SAP Netweave