User id is not processed by BAPI
Hi ,
We are implementing SAP PM and developing interface with PI.
Iam passing userid (technicians) to BAPI for Dismantling/Installation of equipment as to track who has performed the action.
The issue is PI is not taking the userid rather it is processing with the PI system id .
Please suggest to resolve this issue.
Regards
Anil
Hi Pete,
Let me state my problem again...
Xi interface sends a file which will contain data to create equipments. this will contain the user name field . The equipments created/changed by should be with this user ID.
I create set of Equipments(Through BAPI) . My problem is i can create the Equipment with the user id given in the file. but when i use change transaction IE02 , i tried to populate sy-uname with the name given in the file just before call transaction IE02. it is not working.
I tried using BAPI BAPI_EQUI_CHANGE to change the changed by field but no luck.
Any pointers on how to resolve this would be highly appreciated.
Thanks and Regards
Anil Kumar
Similar Messages
-
Full Name(USR_FULL_NAME) is not showing up in User Defn of "OID Process"
I have made the "Full Name" (USR_FULL_NAME) field visible under section "Basic User Information" by going to OIM-UI -> Advanced -> User Configuration -> User Attribute. Note that this 'Full Name' field is not same as out of box 'Common Name' or 'Display-Name'. This is not based on First-Name & Last-Name combination, but a user editable field.
When I configure pre-pop adapter or "OID User" process, I do not see this field in "User Definition" drop-down list. I see all the corresponding fields of USR except this one field. What could be going wrong here ?
Thanks!
KabiThank you all.
Note that, I can see the "Full Name" in create user screen and able to enter data for this field. However, I do not see this field in 'User Definition' drop down list when I try to map it in a pre-pop (or oidMODIFYUSER) adapter.
I checked the attribute lists of all OOB 'Authorization Policy' involving "search user" permission and found the 'Full Name' is already selected. What else I should be looking for ?
Thanks!
Kabi -
Hi.. I am reinstalling ios on macbook.
While doing process, it asks for the Apple id and password. I am providing the id/password but it displays the message that apple user id has not been used with apple store... what shall I do to make my id work. Please assistJust to clarify, iOS is the operating system for iOS based devices such as the iPod touch, iPhone, and iPad.
Your Mac runs on OS X.
As for your Apple ID, help here > Using an existing Apple ID with the iTunes Store, Mac App Store, and iBooks Store -
User Exit RV60AFZZ not Triggered When Processing IDOC
Hi,
I'm writing to seek some advice on why is the user exit RV60AFZZ not getting triggered when I do a vf01 bdc inside my inbouund IDOC function module. But when I try SHDB the user exit is getting triggered normally.
Thanks,
MawiHi,
Yes I'm creating invoice using delivery orders, inside the idoc function module I'm using bdc call transaction vf01 but somehow it does not trigger the user exit.
But when I do manual vf01 in sap, the user exit is getting triggered.
I cant figure out why this is the behavior of sap.
Regards,
Mawi -
Block deleting DMS Document from user that is not initiator
Hi All
Hello
I Want to Block deleting DMS Document ((CV02N)
form all users that are not the initiators of the Document or
Bolcking for all user
for that I created new user authrization for CV01N,CV02N
without authorization for delete
I created a DOC in SPS (production) No 3001591
but I successed to delete the doc through cv02n
in the buttom icon for delete original
There is an option to block any user or specific form delete document ?
If there is no option for that there is an user exit that I can used ?
Thanks in advanse for your helpHello,
it is possible to extract DMS's file to application server directory:
FUNCTION Z_DMS_VIEW.
""Interfase local
*" IMPORTING
*" VALUE(DOC_NUMBER) LIKE BAPI_DOC_DRAW2-DOCUMENTNUMBER OPTIONAL
*" VALUE(DOC_PART) LIKE BAPI_DOC_DRAW2-DOCUMENTPART OPTIONAL
*" VALUE(DOC_TYPE) LIKE BAPI_DOC_DRAW2-DOCUMENTTYPE OPTIONAL
*" VALUE(DOC_VERS) LIKE BAPI_DOC_DRAW2-DOCUMENTVERSION OPTIONAL
*" VALUE(ORIGINAL_PATH) LIKE BAPI_DOC_AUX-FILENAME OPTIONAL
*" EXPORTING
*" VALUE(P_RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*" DOC_FILES STRUCTURE BAPI_DOC_FILES2 OPTIONAL
CLEAR: doc_files.
REFRESH: doc_files.
DATA: i_doc_files like bapi_doc_files2.
DATA: i type i.
i = 2.
while i = 2.
i = 2.
endwhile.
CALL FUNCTION 'BAPI_DOCUMENT_CHECKOUTVIEW2'
EXPORTING
DOCUMENTTYPE = DOC_TYPE
DOCUMENTNUMBER = DOC_NUMBER
DOCUMENTPART = DOC_PART
DOCUMENTVERSION = DOC_VERS
DOCUMENTFILE = i_doc_files
GETSTRUCTURE = '0'
GETCOMPONENTS = 'X'
ORIGINALPATH = ORIGINAL_PATH
HOSTNAME = ' '
GETHEADER = 'X'
PF_HTTP_DEST = 'SAPHTTPA'
PF_FTP_DEST = 'SAPFTPA'
IMPORTING
RETURN = P_RETURN
TABLES
DOCUMENTFILES = DOC_FILES.
ENDFUNCTION.
ORIGINAL_PATH must be a directory of application server.
By background is not possible (I don't know how can we do that) download thsi file to PC.
Then with the file in application server we can :
- to map application server directory in a drive unit of Pc
- to transfer with a ftp client from Pc
- rfcexec
But always the bapi can not download the file: it must be a process in Pc who transfer the file. -
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.. -
User POV does not pop up from Report in task list
Hello,
I've created a report within Related Content in HFM and added it to a task list--the problem I'm experiencing is when I run the report the User POV does not pop up, rather it simply uses the default POV (ie, whatever is set up in data grids or process management)--this happens if I try to run it directly from Related Content or from the task list. My preferences within Financial Reporting have already been updated to 'On' to preview the User POV and if I run the report from Financial Reporting (ie, Explore) the User POV works fine--so, it seems like adding a report to Related Content disables the User POV from popping up. I'm running on Financial Reporting v11.1.2.1 and HFM v11.1.2.1.104.3701. I can't find anything about it within this forum, knowledge base or as a known issue in the ReadMe for the .104 patch set for HFM.
Can anybody fill me in on if this is functionality by design or a defect?
Best regards,
Jason CallFinancial Reports do not work as you might expect when they are used as a related content item. As you already have realized, you will not be able to adjust the FR POV items from inside of HFM.
A 'work around' would be to link to the report and put that link in the Tasklist. This will then open the report 'normally' and you will get the POV functionality that you expect.
To find the link to a report, open the report's properties and look at the 'smartcut' value. (That is a URL directly to the report) -
User "Administrator" does not exist
Hello everybody,
i implemented SP Stack 13 in our Java Instance! Now we got some Problems in our Portal.
1) Selfgenerated IViews cannot be accessed. We got the a Portal runtimeerror. In the Tracefile we found the following message:
#1.5 #0011258C7044006100000253000003EC0004418B74EB8814#1197967124597#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.BWReport',
Context Name (iView): 'pcd:portal_content/every_user/general/ARB/ARB-FI/AR_FI_Role/ARB_QM_REP_0/AR_FI_SY_WEB_KONZUMS_RW_S',
Top Layer: 'BWReport/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'BWTCLNT001',
[EXCEPTION]
#1#com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:455)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>'; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:167)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:407)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:374)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:386)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:107)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:441)
... 30 more
Caused by: java.lang.ClassCastException
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.getProducerByAlias(AppIntegratorInformationService.java:126)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.buildFPNLocatorForShortcut(AppIntegratorInformationService.java:142)
at com.sap.portal.fpn.runtime.services.AppIntegratorInformationService.transformURL(AppIntegratorInformationService.java:204)
at com.sapportals.portal.appintegrator.template_processor.context.FPNWrapper.getTerminal(FPNWrapper.java:69)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:152)
... 45 more
#1.5 #0011258C7044006100000255000003EC0004418B74EC9CB6#1197967124690#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:09:38_18/12/07_0005_18713950
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/every_user/general/ARB/ARB-FI/AR_FI_Role/ARB_QM_REP_0/AR_FI_SY_WEB_KONZUMS_RW_S
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : TESTUSER1
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>&\#39;; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
#1.5 #0011258C7044006100000257000003EC0004418B74EEE9EF#1197967124894#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#TESTUSER1#36624##srv053_BWT_18713950#Guest#95ba2ce0ad4411dcbf910011258c7044#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Java###09:38_18/12/07_0005_18713950
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.scheme>://<System.servername>:<System.serverport><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-bw-iViewID=<FPN.PCDHomeLocation[url_ENCODE]>&sap-ext-sid=<ESID[url_ENCODE]>&sap-pp-producerid=<producerID>&sap-pp-consumerBaseURL=<Request.BaseURL[url_ENCODE]>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<BusinessParameters>&\#39;; the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
2) In the Trace file all the Time occurs the following message:
#1.5 #0011258C7044006F0000027A000003EC0004418B678FE974#1197966900571#com.sap.workflow#sap.com/irj#com.sap.workflow#J2EE_GUEST#0####8f2fa3e0aa4d11dcb0150011258c7044#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/Workflow/General#Plain###TaskSchedulerDeadline.run()#
#1.5 #0011258C7044006F0000027B000003EC0004418B678FEBD8#1197966900571#com.sap.workflow#sap.com/irj#com.sap.workflow.#J2EE_GUEST#0####8f2fa3e0aa4d11dcb0150011258c7044#Thread[ThreadPool.Worker4,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.security.api.NoSuchUserException: User "Administrator" does not exist.
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1635)
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1574)
at com.sap.security.core.imp.UserFactory.getUserByUniqueName(UserFactory.java:1560)
at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:90)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)
at java.lang.Thread.run(Thread.java:534)
Can somebody tell me what is going on here?
Thanks so long
Edited by: Oliver Heinzelmann on Jan 11, 2008 2:17 PM
Problem #1 resolved: Ask me for solutionHi Oliver,
A contact at SAP has indicated that in the KM Task Scheduler Deadline (com.sap.workflow.es.scheduler.TaskScheduler.Deadline.run) that the user "Administrator" is hard coded in the SPS13 release.
Depending on what you are using the KM for you could reduce the frequency of the alert by changing the scheduling of this task which by default is every five minutes.
Although the release notes of the following patches didn't formerly address the hard coding issue, I decided to apply them anyway as I thought that a later release may have fixed the issue. However it is not fixed with these interim patches.
KMCBC13P_1-10003491.SCA Patch for KMC BASE COMPONENTS 7.00 SP13
KMCCM13P_1-10003492.SCA Patch for KMC CONTENT MANAGEMENT 7.00 SP13
I guess we will need to wait for a further patch to be released and ignore the error in the meantime.
Regards
Craig -
Can't enroll device for user and this user account is not authorized to use Windows Intune.
Hello,
We have SCCM 2012 R2 inegrated with intune via an intune subscription. When I enroll a device with my admin account there are no problems, but when I want to add it with another user account which is a member of the Intune users collection, it can't be enrolled.
When I tested on https://portal.manage.microsoft.com with the credentials of the user I couldn't connect and received the following error: This user account is not authorized to use Windows Intune.
Do I have to do anything in the https://accounts.manage.microsoft.com as there is a checkbox saying Windows Intune. this is unchecked now for all the users even my own account on which I'm able to enroll a device.
Or is this a license problem? I know configuration Manager uses licenses for Intune but where can we track how many licenses are used and how many available? Is there some kind of report available?
I hope someone can help me
Kind regards,
RobbenI added them yesterday and this morning I was still not able to enroll a device with the added user his credentials.
The UPN is correct. Maybe I need to force the DirSync then? Or will one day of waiting be enough normally?
I can see the user in the intune management portal. Does this means it has been synced?
Another thing I noticed is the cloudusersync.log doesn't show them being added? What I was thinking is I first used the all Users collection in the subscription and afterwards I changed it to a specific collection with only the test users. Could it be that
they all synced already and the log doesn't show them anymore?
A warning in this log shows this also:
WARNING: Failed to get lsu url. default release one will be used. exception = System.NullReferenceException: Object reference not set to an instance of an object.~~ at Microsoft.ConfigurationManager.DmpConnector.UserSync.CloudUserUpload..ctor()
SMS_CLOUD_USERSYNC 23/04/2014 15:02:18 7684 (0x1E04)
I don't know if that has anything to do with this?
this is an extract of that log:
CCloudUserSync::Process - User sync processing thread is now stopping. SMS_CLOUD_USERSYNC 23/04/2014 14:59:42 8144 (0x1FD0)
SMS_EXECUTIVE started SMS_CLOUD_USERSYNC as thread ID 7684 (0x1E04). SMS_CLOUD_USERSYNC 23/04/2014 15:02:15 7572 (0x1D94)
CCloudUserSync::Process - User sync processing has started. SMS_CLOUD_USERSYNC 23/04/2014 15:02:15 7684 (0x1E04)
Starting user sync ... SMS_CLOUD_USERSYNC 23/04/2014 15:02:15 7684 (0x1E04)
WARNING: Failed to get lsu url. default release one will be used. exception = System.NullReferenceException: Object reference not set to an instance of an object.~~ at Microsoft.ConfigurationManager.DmpConnector.UserSync.CloudUserUpload..ctor()
SMS_CLOUD_USERSYNC 23/04/2014 15:02:18 7684 (0x1E04)
Starting user delta sync, raise failure status messages = True SMS_CLOUD_USERSYNC 23/04/2014 15:02:18 7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:02:19 7684 (0x1E04)
Successfully removed users from cloud 0 SMS_CLOUD_USERSYNC 23/04/2014 15:02:19 7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:02:19 7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:02:19 7684 (0x1E04)
Starting user delta sync, raise failure status messages = True SMS_CLOUD_USERSYNC 23/04/2014 15:07:19 7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:07:19 7684 (0x1E04)
Successfully removed users from cloud 0 SMS_CLOUD_USERSYNC 23/04/2014 15:07:19 7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:07:19 7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:07:19 7684 (0x1E04)
Starting user delta sync, raise failure status messages = True SMS_CLOUD_USERSYNC 23/04/2014 15:12:19 7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:12:19 7684 (0x1E04)
Successfully removed users from cloud 0 SMS_CLOUD_USERSYNC 23/04/2014 15:12:19 7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:12:19 7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:12:19 7684 (0x1E04)
Starting user delta sync, raise failure status messages = True SMS_CLOUD_USERSYNC 23/04/2014 15:17:19 7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:17:19 7684 (0x1E04)
Successfully removed users from cloud 0 SMS_CLOUD_USERSYNC 23/04/2014 15:17:19 7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:17:19 7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:17:19 7684 (0x1E04)
Starting user delta sync, raise failure status messages = True SMS_CLOUD_USERSYNC 23/04/2014 15:22:19 7684 (0x1E04)
Total received users from SCCM to be removed from cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:22:19 7684 (0x1E04)
Successfully removed users from cloud 0 SMS_CLOUD_USERSYNC 23/04/2014 15:22:19 7684 (0x1E04)
Total received users to add from SCCM = 0, Total Successfully added users to Cloud = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:22:20 7684 (0x1E04)
UserDeltaSync:- Users Added = 0, Users Removed = 0 SMS_CLOUD_USERSYNC 23/04/2014 15:22:20 7684 (0x1E04)
kind regards,
Robben -
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550
Hi Experts,
We have many File to EDI scenarios wherein XI System pick up the XML and sent to customers via EDI. Recently we faced a problem so created a Back-up System (Production copy) and tested successfully. After sometime the messages were routed to this back-up system and when we notice it and then stopped the back-up system. All the messages that were routed to back-up system, we try to send the same messages from the actually Production system to our customers. Now the problem is XI system (Production system) is unable to pick these files and I check the communication monitoring and encountered the below error message.
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550.550
Can anyone let me know how to fix the issue or what needs to be done?
Your help is highly appreciated.
Regards
FaisalHi,
It seems to be problem with permission of files. Please ask your basis to do following:
1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
Regards
Aashish Sinha -
User weblogic is not permitted to boot the server
Hi,
I am new to OES and after running the configtool, creating the ASIAuthorizationProvider and ASIRoleMapperProvider (both has Defaul Identity Directory: wls_dir and Application Deployment Parent: //app/policy/wls_app), binding the SSM, i get this error when starting the WLS admin server:
15:33:26.312 EVENT Starting Jetty/4.2.25
15:33:26.859 WARN!! Delete existing temp dir C:\BEA_HOME_10\ales32-ssm\wls-ssm\i
nstance\wls_ssm\work\jar_temp\Jetty__8000__ for WebApplicationContext[/,jar:file
:/C:/BEA_HOME_10/ales32-ssm/wls-ssm/webapp/arme.war!/]
15:33:30.515 EVENT Started WebApplicationContext[,ARMEService]
15:33:32.562 EVENT Started SocketListener on 0.0.0.0:8000
15:33:32.562 EVENT Started org.mortbay.jetty.Server@176bf9e
ARME is started now
<Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm wls.>
<Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <BEA-090404> <User weblogic i
s not permitted to boot the server; The server policy may have changed in such a
way that the user is no longer able to boot the server.Reboot the server with t
he administrative user account or contact the system administrator to update the
server policy definitions.>
<Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server su
bsystem failed. Reason: weblogic.security.SecurityInitializationException: User
weblogic is not permitted to boot the server; The server policy may have changed
in such a way that the user is no longer able to boot the server.Reboot the ser
ver with the administrative user account or contact the system administrator to
update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitte
d to boot the server; The server policy may have changed in such a way that the
user is no longer able to boot the server.Reboot the server with the administrat
ive user account or contact the system administrator to update the server policy
definitions.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown S
ource)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FAILED>
<Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <BEA-000383> <A critical s
ervice failed. The server will shut itself down>
<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to FORCE_SHUTTING_DOWN>
Stopping PointBase server...
PointBase server stopped.
from the WLS AdminServer.log:
####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000436> <Allocating 3 reader threads.>
####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000446> <Native IO Enabled.>
####<Mar 5, 2010 3:33:06 PM SGT> <Info> <IIOP> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774386531> <BEA-002014> <IIOP subsystem enabled.>
####<Mar 5, 2010 3:33:11 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774391656> <BEA-000000> <Starting OpenJPA 1.0.0.1>
####<Mar 5, 2010 3:33:17 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774397171> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413421> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413500> <BEA-090663> <The DeployableRoleMapper "com.bea.security.providers.authorization.asi.RoleProviderStub" implements the deprecated DeployableRoleProvider interface.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413531> <BEA-090662> <The DeployableAuthorizer "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" implements the deprecated DeployableAuthorizationProvider interface.>
####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm wls.>
####<Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090082> <Security initializing using security realm wls.>
####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774414234> <BEA-090404> <User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414234> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FAILED>
####<Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Mar 5, 2010 3:33:34 PM SGT> <Info> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414359> <BEA-000236> <Stopping execute threads.>
also, i just noticed that when staring OES admin server i get the following from the logs:
system_console.log:
2010-03-05 15:19:04,218 [JettySSLListener1-1] ERROR com.wles.soap.BLM.BlmBindingImpl - getUndistributedAttributeChanges has not been implemented properly.
2010-03-05 15:27:17,656 [Thread-31] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
Communication Error:; nested exception is:
javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme group '//bind/wls' error report, policyno = 52:
2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme 'asi.null.ARME.wls_ssm.asi.SGBLM010':
2010-03-05 15:27:33,015 [Thread-32] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
2010-03-05 15:27:33,015 [Thread-32] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
Communication Error:; nested exception is:
javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
WLESWebLogic.wrapper.log:
INFO | jvm 1 | 2010/03/05 15:27:17 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
INFO | jvm 1 | 2010/03/05 15:27:17 | Re-throwing the fault...
INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: Client has closed the connection, error not reported to client.
INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: The exception is: com.bea.wles.management.console.utils.NestedJspException: Connection reset by peer: socket write error
INFO | jvm 1 | 2010/03/05 15:27:33 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
INFO | jvm 1 | 2010/03/05 15:27:33 | Re-throwing the fault...
although, it seems that the OES admin server is up since i am able to access the OES admin console.
i have tried playing around the policies to grant the "weblogic" the priviliges for an Admin but is still get the same issue. Although, when i try to distribute the changes in the policy, "ASI ( Policy for entire Oracle Entitlements Server system ) " still appears in the list of changes.
any thoughts on what the problem is? is there a way to force the distribution of the policy? maybe through the command prompt or other console?
Edited by: user9056644 on Mar 5, 2010 12:02 AMHave you applied CP2 or CP3 to OES? There were enhancements that allows these policies to be scoped within an organization. I only ask to help guide you on distributing policies for the runtime WLS domain. The ASI domain is only for the admin. There should have been a set of resources and policies created as a result of running ConfigTool for your new instance (looks like you named it 'wls'). If no CP, it will be in DefaultApp next to ASI.
You have to distribute policies for 'wls' immediately following running ConfigTool before starting WebLogic or you will put it into a state where it can't be started. The corrective action is to remove the state.ck file under C:\BEA_HOME_10/ales32-ssm/wls-ssm/instance/wls_ssm/work/runtime, distribute policies, restart WebLogic.
If you need to re-run ConfigTool (after installing CP for instance), revert the following files:
<domain>/config/config.xml
<domain>/bin/startWebLogic.sh | .cmd
Revert from the no-ales backups created. Remove the instance folder under C:\BEA_HOME_10\ales32-ssm/wls-ssm/instance. You can then re-run ConfigTool if you have to. -
Lync 2013 client not processing history spooler folder (conversation history)
We have been using Lync 2013 fully patched up to latest & greatest, along with Exchange 2013 for about 6 months now & everything is working
great. (I did a AD migration from our old parent company in the UK as well as migrated exchange from 2010 to 2013, all that without a hitch for the most part.)
the issue that seems to be popping up intermittently is conversation history. I manged to work around some of them for the most part & getting
them to process; with the exception of 1 user.
If he logs into another PC his conversation history works fine.
However on his PC it does not seem to want to process the history spooler folder in "C:\Users\User\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]m",
there are 737 files in there (all of his convo history)
Now what i did & it seems to sort of work is,Signed out of Lync, I deleted the users Sip folder after backing up the history spooler folder, logged
back into Lync which recreated the sip_user folder; logged back out of Lync , copied the History Spooler folder back to the SIP folder, & signed into Lync.
This took 10 files out of the history spooler folder, & then appeared in the convo history; both on Lync client & Outlook; but did not bring
all of them in. I did some testing and if you log out, then back in, it processes a few more. but not all.
EWS & MAPI settings & all other Lync configuration information settings match a users with no convo history issues.
So now the questions.
1)What could possibly cause what ever mechanism that processes the History spooler folder to stop/only process a few items during sign in? Also what
is the mechanism?
2)Is there any way through powershell to force the synchronization of the history spooler folder?
Thank youso in some more testing i had check the history spooler folder, & there were about 700+ files.
as a note* (Upon deleting the users sip folder & logging back in thus re-creating the folder new convo's where saving. So i did "fix" the issue with no new convo's during my initial work prior to opening this thread.)
I then removed a good chunk of the *.hist files & only left convo's from this month. signed out then back in, 10 files processed. then did it again, another 10. did it again, & it did 4 then stopped. I noticed there were some files over 1 mb. &
remember coming across this post (Lync
not processing files over 1mb) so i removed the 1mb files & then logged out then back in. processed 10 more.
i then added all the files to the history spooler file with the exception of the files over 1 mb, & logged in & out about 70 times to process the whole folder. Now all of the convos are in Lync & outlook as well as new convo's being saved. However
i have a folder now with 130 files that are over 1mb that will not process at all..
so now i am trying to find some validity on the statement in the link above
"We did open a case with Microsoft and they confirmed it is a bug in the Exchange EWS HTTP stack. It
is supposedly under review by the Dev team, but my guess is that it won't be fix soon. The magic size is exactly 1MB or 1048576 bytes."
If that is actually true it sucks & is some B.S as it is nearly 2 months later & this is obviously
a major problem & not even a CU or PU has been released to address the issue. -
IDOC is not processing in R/3 with status 64(Urgent)--Production issue.
Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
In data selection tab, I given date as from 2002 to 2003
In Update tab, I selected update mode as Initialize Delta process- without data transfer and Uncheck Update Data in master system immediately
In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier. -
AT USER COMMAND is not getting triggerd
Hi Techie's
I have two fields on the selection screen
1) Name: ___________
2) Id: ___________
I have some buttons say on the Application toolbar say::
Save Delete Modify Exit
I have created these buttons in the INITIALIZATION event.
I am using AT Selection Screen OUTPUT for some logic purpose.
Later I am writing AT USER COMMAND and pressing SAVE The function code for SAVE is "SAV".
But the drama is that AT USER COMMAND is not getting triggered at all.
It goes first to Initialization--->At selection Screen OUTPUT>Then screen appears> I give the values and press the SAVE button--
again it goes to the At Selection screen OUTPUT.
Not even getting the hang of it. Please help if anybody know the story of it.
ITS SO URGENT.At user command is for list processing, you need something like this:
Pushbuttons in the Application Toolbar
In the application toolbar of the standard GUI status of the selection screen, five pushbuttons are predefined with the function codes FC01 to FC05, but are inactive by default. You can activate them during the definition of the selection screen as follows:
SELECTION-SCREEN FUNCTION KEY i.
The numbering i must be between 1 and 5. The individual function texts must be assigned to the functxt_0i components of structure sscrfields before the selection screen is called. You must declare this structure as an interface work area using the TABLES statement.
If the user chooses one of these buttons, the runtime environment triggers the AT SELECTION-SCREEN event and the function code FC0i is placed into the component ucomm of the structure sscrfields.
After the AT SELECTION-SCREEN event has been processed, the system displays the selection screen again. The only way to exit the selection screen and carry on processing the program is to choose Execute (F8). Consequently, the pushbuttons on the application toolbar are more suitable for controlling dynamic modifications of the selection screen than for controlling the program flow.
REPORT demo_sel_screen_function_key.
TABLES sscrfields.
PARAMETERS: p_carrid TYPE s_carr_id,
p_cityfr TYPE s_from_cit.
SELECTION-SCREEN: FUNCTION KEY 1,
FUNCTION KEY 2.
INITIALIZATION.
sscrfields-functxt_01 = 'LH'.
sscrfields-functxt_02 = 'UA'.
AT SELECTION-SCREEN.
CASE sscrfields-ucomm.
WHEN'FC01'.
p_carrid = 'LH'.
p_cityfr = 'Frankfurt'.
WHEN 'FC02'.
p_carrid = 'UA'.
p_cityfr = 'Chicago'.
ENDCASE.
START-OF-SELECTION.
WRITE / 'START-OF-SELECTION'.
This defines a standard selection screen with two parameters. In the application toolbar, two pushbuttons are assigned the texts LH and UA and activated.
When the user clicks one of the buttons, the AT SELECTION-SCREEN event is triggered and there the input fields are preassigned correspondingly. -
Script Alert: "Sorry I could not process the following files" (Error Message using Image Processor)
I'm a seasoned Photoshop/Bridge CS5 user who recently upgraded to CS6. In Bridge I just ran my first Image Processor batch, trying to convert a set of RAW .NEF files to .PSD files with a basic editing action I created applied to them. Photoshop CS6 opens the files from Bridge and applies the actions, but then I get the "Script alert" error message "Sorry I could not process the following files" and a list of all of the files in the batch I was trying to run the script on. The files all remain open and are saved on my hard drive in a folder created by the Image Processor script, but do not close unless I manually close them. I never had this problem in CS5 where the image processor would apply the desired actions to the batch of photos one at a time, then save and close. Thoughts on how I can fix this bug?
Hey Jeff--
No specific action steps to make the image safe - no flattening, etc. Had problems narrowing down the specific action step causing the problem. So I ran the Image Processor script in the ExtendScript ToolKit and debugged in. (I'm using the version that shipped with CS4.)
Turns out what was happening is that the app.activeDocument.close() command on line 1490 was never getting called, because the this.SaveFile() above it was throwing an exception. More debugging got me to the problem - SaveFile() tries to restore the history state after making a doc safe for saving as a JPEG. This causes an exception. So I commented out line 1571:
// app.activeDocument.ativeHistoryState = historyState;
The script runs just fine after this. I commented out the close to see what history states got added to the doc, but no new states are recorded, so commenting out the restore line should not cause any problems.
Of course, my solution does not solve the problem and I may need to comment out all the saveFile() lines that does this. Not sure why some actions have this problem and others don't. The actions I am running have about 25 steps. Perhaps PS is not catching up quick enough. I added a $.sleep(2500) after the restore history but that didn't help.
So, not sure where this gets us. I will check about posting an action set with just one of the actions that cause the problem. But I may also have our customer comment out that line of the Image Processor script.
Hope this helps. May post more next week.
Maybe you are looking for
-
Macbook Pro Retina 15" 2014 et Illustrator CC fluidité ??
Bonjour, Je viens d'acquérir un MBP Retina 15" haut de gamme (i7, 16gb de RAM, 512 SSD, GeForce GT 750M 2gb) avec un système parfaitement propre avec Photoshop et Illustrator CC d'installés. Ce dernier est terriblement saccadé (défilements/navigation
-
Xcode 6.1.1 Custom Class Outlets Missing
I'm running through the basic Apple tutorial on iOS App Development https://developer.apple.com/library/ios/referencelibrary/GettingStarted/RoadMapi OS/index.html#//apple_ref/doc/uid/TP40011343-CH2-SW1 Running Xcode Version 6.1.1 (6A2008a) After crea
-
Connecting to a Panasonic TX-26LXD52 LCD TV
Hi, I've been experimenting connecting my Powerbook (1.67Gz) to the Panasonic TV via SVideo cable. The problem is the best resolution on the TV I am getting is 1024x768, yet the TV is capable of showing 1366x768. I've tried fiddling with SwitchResX b
-
10gLiteR3 publishing ORA-00942: table or view does not exist error
Hi All, I am encountering table or view does not exist error while publishing using the api. Below is the code: try { consolidatorManager.openConnection("MOBILEADMIN","PASSWORD", ADMIN_JDBC_URL); mobileResourceManager = new MobileResourceManager("MOB
-
Running 10.5.5 on a brand new xServe. Seriously.. what is wrong with leopard server? This is my first experience with it and I am not happy. I am simply running AFP with 4 share points. No other services. Clients get disconnected for no reason. Clien