Workflow Definition For SUS Invoice BUS2234

Hello Guys:
One quick question, is it possible to create a WF for the invoice which is created by the Supplier?? I mean for the BUS2234 Object. I have been looking trough the SAP Workflow configuration and there is no standard WF for this document.
Thanks
Hugo

Hello Guys, thanks for the answers, yea the Business Process is similar the one you have described.  Supplier creates de invoice in SUS and the Invoice Manager and Financials department should approve before it could be send to the back end. We are implementing the ECS.
I know the BOR is the BUS2234 so it is possible to trigger the WF using this object?
Thanks for all your help Guys.
Hugo

Similar Messages

  • SUS-EBP scenario. SUS Invoice not transfered to EBP

    Hi all.
    I try to customize SRM 7.0 with SUS on different clients.
    XI Integration scenario (service procurement) is activated and works fine except SUS invoice replication to SRM. I can see in XI (tr. SXI_MONITOR) XML's for PO's, SUS PO's, Confirmations but not for Invoices.
    When I create SUS Invoice and sent it system doesn't generate any XML (no XML in SRM and XI at all).
    Can somebody help to resolve this problem? or simply provide me with abap-program name which is start output(XML) generation for SUS Invoice?

    Hi Mikhal,
    Please check if the invoice triggering event is defined or not ?
    SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Event and Event Schema for Alert Management -->Define Events
    Add u2013 event definition u2013 INVOICED for object type - BUS2234
    This should trigger the Invoice.
    Thanks,
    -Devi Swain

  • Deleting Workflow definition

    I am thinking of using script wfrmitt.sql to drop the design and run time information for one specific item type.
    After the delete I am planning to apply the new workflow definition for the same item type.
    This is because changes made to the workflow objects are not reflecting in my test instance.
    Pl. advise if there is better way of updating the workflow definition.
    Thanks

    Figured it out. I don't need to delete the definition. See my other posting @ Workflow changes not reflected
    Sorry for the confusion.

  • Std workflow for Parked Invoices?

    hi guys
    are there any std workflows for parked invoices? Our requirement is that once the Finance clerk creates a customer or vendor invoice he should only be able to park it and not post the invoice. Once the invoice is parked then the system should trigger a workflow and a notification neeeds to be sent to the approver to approve the invoice. Once it is done the finance clerk will post the invoice.
    I switched on the event trace and did a trace on while creating a parked invoice. No event is triggered when the document is parked. If i post the document the event POSTED of object FIPP is triggerd. So since we dont have any std events raised when a document is parked is it possible to have a workflow?

    Hi,
    The event FIPP.CREATED is raise via the customizing (SPRO)
    Financial Accounting -> Financial Accounting global setting -> document -> document parking -> create workflow variant for parking documents.
                                      Assign co.code to a workflow variant for parking documents.
    Have a look at ws10000051.
    Regards,
    Ronit.

  • SAP Workflow for vendor invoice is posting into past?

    Dear experts
    I have a heavy problems with the workflow for vendor invoices. The following example demonstrates it:
    I have created a vendor invoice on 1st of December 2011.The responsible person has checked and released this invoice on 3rd January 2012. In Customizing it is setup that posting date will be overwritten with system date.
    Does anybody has an idea why it is not posted in January 2012?
    What does the workflow? It is posting that invoice with posting date 1st December 2011 not with 3rd January. If I have a closer look into the head of the SAP document the following parameters are shown: document date: 1st December, posting date: 1st December, entry date: 3rd January.
    Does anybody has an idea why entry date is 3rd January?
    Thanks in advance
    Udo

    Dear expert
          It is not standard behavior for the posting date to overwrite the document date - at least its not something that I've ever come across. I'm wondering if there is a custom substitution on your system that is overwriting the document date . Check t-code OBBH. The substitution is most likely at the document header level.
    Regards
       Ajeesh.s

  • Price variance workflow for blocked invoices in MM purchasing

    Hi Gurus,
    We are implementing price variance workflow for blocked invoices. We built a custom workflow to
    take care of the routing requirement of the customer.
    We also did necessary customization defining the tolerance limits for price variance. Before testing the workflow wanted to check events in SWEL and its is found that system doesn't raise any event for price/ quantity block and hence the workflow is not triggered at all.
    Event trace active flag is set in SWELS. I am not able to figure out what we are missing.The invoice gets created correctly with the price/quantity blocks and blocked invoices are available when we see in Tcode 'MRBR'.
    Any suggestion will be highly appreciated.
    Edited by: srinivas bejjanki on Jan 29, 2009 10:34 PM

    Hello,
    So you are absolutely sure the event trace is on. If you try SWUE with some other event, you see the entry in SWEL, dated a few minutes ago, correct?
    When you try SWUE with BUS2081.BlockedPrice does it give any message?
    Does SWUE work with any other BUS2081 event?
    regards
    Rick Bakker
    Hanabi Technology

  • Check for duplicate invoices and trigger a workflow

    Hello All,
        I have a requirement to check for duplicate invoices in AP(Accounts payable) and trigger a workflow when duplicate invoices are found. I a not sure how to do any of the above. Please  let me know if you have any information on:
    1) Checking for duplicate invoices in AP
    2) Trigger a workflow
    Are there any standard workflows that checks duplicate invoices?
    Thanks.
    --Mithun

    Hi MD,
    I doubt if system gives an error on FI side when a duplicate invoice is posted.
    I feel you would require a BAdi for it, where you can call your WF using FM SAP_WAPI_START_WORKFLOW.
    Hope it helps.
    Aditya
    P.S also ask your Func Consultants, if there are any settings in the Customization, where you could capture Inv Dt, Inv Amt, Vendor, Company code.
    Edited by: Aditya Varrier on Oct 15, 2008 9:38 AM

  • Trigger workflow for MIRO invoice creation

    Hello,
    In standard functionning it is not possible to trigger the workflow for documents coming from MM.
    When using transaction MIRO and selecting invoice creation the created document has following value :
    BKPF-AWTYP = 'RMRP'. whereas creating it from FB60 results to BKPF-AWTYP = 'BKPF'.
    The problem is standard code checks AWTYP is not equal to 'RMRP' before creating event to start the standard workflow for invoice validation.
    Question : why sap doesn't allow workflow creation for invoices from MIRO?
    Thanks for your answers.
    Best regards,
    Laurent.

    Hi,
    here they are...
    WS20000397 MMIVBlockedP Treatment of inv. blkd for price, Log.IV
    WS20001004 MMIVToRel Release the Completed Log. IV Document
    WS00400026 MMIVquantity Treatment inv.blocked f.quantity reasons
    WS20001003 MMIVToCompl Complete the Parked Log. IV Document
    WS00400027 MMIVprice Treatment invoic.blocked f.price reasons
    All of these workflows are a one-step / one-level of approval and needs some workflow configuration at least for the agent assignments. For a full-blown workflow you should take these workflows as an example, how you could work with it.
    The last two workflows work with preliminary posting on the miro (transaction MIR7).
    Best regards,
    Florin

  • FV65 - WorkFlow Implementation for parking and posting invoices

    Hi All,
        We are implemetnig workflow for vendor invoices. can anyone implemented this for FV65 can help us which workflow template to use and what are the configuration settings for this.
    Regards
    Purna

    Hi:
    Refer to this documentation.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
    Please let me know if you need more information.
    Assign points if useful.
    Regards
    MSReddy

  • Workflow for Reversing Invoice (FB08)

    Hi Gurus,
                  We are configuring Payment Release workflow for our project.
                  I am using the standard Workflow WS00400012  for the same and its working fine.
                  In the above mentioned workflow, if the payment release is rejected it will go the next step 'Change document line'
                  to change the line item and post again.
                  But now the requirement is, once the payment release is rejected system should do the invoice reversal for that
                  document (FB08).
                  Is this possible by customizing the standard workflow ?
                  If so, is there any business object or workflow to reverse invoice through FB08.
                  Please suggest me.
                   Thanks in advance,
                   Santosh.

    Hi Suresh,
                   Thanks for the reply.
                   I have checked those methods to display and edit documents.
                   Actually they are calling the Transaction code  directly and we can change the data manually and save.
                   But we want the workflow should take care of the reversing invoice without manual interaction.
                   Can i use any BAPI or FM in my custom method to meet my requirement ?
                      Thanks in advance,
                      Shyam.

  • Workflow for SD Invoices

    Hello All,
    I have a requirement wherein I need to trigger a workflow on the creation/change (VF01/VF02) of the Invoices.Is there is a standard workflow available for the same which I can make use of ?
    Any pointers would be very helpful.
    Thanks in Advance.
    Regards,
    Sowmya.

    Hi Somya,
    You can check to find if any worfklow is already been assinged to the tranasation VF01/VF02. By using the Transactions:
    SWELS---> Activate / Deactivate the Events.
    Now execute the tranasction with the same way as you need.
    once you execute the transaction you now execute the transaction
    SWEL----> to chekc if any event is triggered or not.
    if not then you can go to the SPRO configuartion  and Next, navigate to SPRO -> SAP Reference IMG and then go to the respective module you want and check if any workflow is activated or not .

  • R11:RECEIVED ERROR MESSAGES FOR AP INVOICE APPROVAL IN ORACLE WORKFLOW

    Hi All,
    We have this error:
    ### Detailed Problem Statement ###
    Received the following error messages in sysadmin notifications:
    Event Error Name: 100
    Event Error Message: ORA-01403: no data found
    Event Error Stack: HZ_DQM_SYNC>REALTIME_SYNCH(oracle.apps.ar.hz.DQM.realtimesync,
    30665979B704AE043C0A81404B04A)
    Event Error Name: WFE_DISPATCH_RULE_ERR
    Event Error Message: [WFE_DISPATCH_RULE_ERR] ENAME=oracle.apps.ap.payment EKEY=10001
    RULE=ap_payment_event_wf_pfg.rule_function SQLCODE=100 SQLERRM=ORA-01403: no
    data found
    Event Error Stack: WF_Event.dispatch_internal()
    In addition, during the set-up of Oracle Approvals Management, there was no available list of
    values in the Notification Style in the workflow configurator page.
    Action Plan
    =======
    1) Confirm if the workflow is customized in any way.
    2) Confirm whether you are able to select global preferences for the other invoices approval, meaning are you
    getting the list of values for the other invoices.
    There are no workflow customizations. We are trying to implement it to AP invoice
    approval only.
    Can you instruct me on how to test this one? I thought I could only select the global preferences from the workflow configuration window. And there are no distinction as to which invoice approval
    process it is applicable. Where could I select the global preferences for other
    invoices approval?
    Thanks a lot

    thanks hussein , but still we can not see LOV values even if we inserted data manually...:(
    But it has improved and we moved on to another error which is:
    *****received the error message:3120: Activity 'APINV/52822' has no performer
    ### Problem description or inquiry details ###
    Received the following error message:
    Error Message
    3120: Activity 'APINV/52822' has no performer.
    Error Stack
    Wf_Engine_Util.Notification_Send(APINV, 115191_1, 52822, APINV:APINV_MRA) Wf_Engine_Util.Notification(APINV, 115191_1, 52822, RUN)
    Encountered the following:
    No list of values in the notification style field in the global configuration region in the Workflow Configuration Page
    Please note that we could not update the workflow configuration page using the forms because there
    is no list of values to select in the above-mentioned field. We just recently
    changed the workflow administrator role from SYSADMIN to KCAALIM to reduce
    changing of user log-in. We have previously used the sysadmin user log-in to
    access the workflow configuration page. there was still no list of values for
    the notification style. we changed the wf admin role to kcaalim using the sql:
    udpate wf_resources set text = 'KCAALIM' where name like 'WF_ADMIN_ROLE';
    Commit;
    Hence, changing of wf admin role and user log-in (to sysadmin) won't help (just in case you would advise me to do so) since we tried it
    already.
    ### Responsibility and navigational paths to reproduce ###
    1. set-up the AME for ap invoice approval.
    2. test an actual transaction.
    3. when the list is generated, set-up workflow for AP approval.
    when setting up the configuration page, there is no list of values available for the notification style. hence the workflow
    configuration could not be updated.
    4. Run the required programs (i.e., synchronizations)
    5. run the approval workflow from the developer studio page.
    6. review the status from the Status Monitor page.
    7. The error message appears
    8. payables, create a sample invoice.
    9. validate and initiate approval.
    10. review the approval history to find out the required approver. (the approver's name appears with 0 amount of approval)
    11. check the notifications in the required approver's worklist.
    12. there are no notifications sent.
    Text continued in next action...
    **** screen shots availble >http://rapidshare.com/files/176008682/error_-noperformer.doc.html
    Thanks again...

  • Tables for vendor invoice and payment

    Hi Gurus.
    I want to know from which tables i can get the information for folllowing points.
    1.       Vendor Invoices  - Complete (Header and Item)
    2.       Vendor Payments Details – Detail about payment method (check, wire, etc)
    Please tell me tje table names.

    There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
    |Table Name               |Table Description                                           |
    |/BEV3/CHKOMPAZVV         |Append Structure CH -> CO PA                                |
    |/CWM/ACCIT               |Append Structure for Enhancement of Structure ACCIT in CWM  |
    |/CWM/KOMP                |Catch Weight Management Enhancement                         |
    |/DSD/TAXJURCD            |Ship From Tax Jurisdiction Code: for Header Prc Comm Str    |
    |/SAPNEA/J_SC_LFA1        |Subcontractor Information                                   |
    |/SAPNEA/J_SC_LFB1        |Subcontracting Management                                   |
    |/SAPPSPRO/A_FI2_LONGNUM  |IBU-PS:  Append structure for structure NONBSEG             |
    |/SAPPSPRO/A_LONGNUMBER   |additional fields for SPIIN number                          |
    |/SAPPSPRO/EADD           |Purchasing Document Header: Additional Data                 |
    |/SAPPSPRO/EADD_DATA      |Purchasing Document Header: Data Part Additional Information|
    |/VSO/R_KNA1_A            |Append to KNA1 for Vehicle Space Optimization               |
    |/VSO/R_KNA1_I            |Additional Data for Vehicle Space Optimization for KNA1     |
    |AACCHD_FMFG              |US federal fields                                           |
    |AACCHD_PSO               |IS-PS: ACCHD Append Structure for Payment Requests          |
    |AACCIT_GM                |Append for Grants Management                                |
    |AACCIT_PSO               |IS-PS: ACCIT Append Structure for Payment Requests          |
    |AACCIT_SSP               |Append for Payment Statistical Sampling Process             |
    |AACCIT_USFG              |Append structure for US federal government                  |
    |AAUSZ_CLR_USFG           |Clearing information for US Fed (Tresury Confirmation)      |
    |ABKPF_PSO                |IS-PS: BKPF Append Structure for Payment Requests           |
    |ABKPF_UMB                |IS-PS: Append Structure for Transfer Transaction FMITPO     |
    |ABSID_PSO                |IS-PS: Data appendix of open items customers                |
    |ABSIK_PSO                |IS-PS: Data appendix of open items vendors                  |
    |ABSIS_PSO                |Local Authorities                                           |
    |ABUZ                     |Help Structure for Line Items to be Generated Automatically |
    |ACCCR                    |Accounting Interface: Currency Information                  |
    |ACCCR_FKEY               |Key: Acctg Currency Data for Line Item Including Currency   |
    |ACCCR_KEY                |Key: Accounting Currency Data for Line Item                 |
    |ACCFI                    |Interface to Accounting: Financial Acctg One-Time Accts     |
    |ACCHD                    |Interface to Accounting: Header Information                 |
    |ACCHD_KEY                |Key: FI/CO Document Header                                  |
    |ACCIT                    |Accounting Interface: Item Information                      |
    |ACCIT_EXTENSION          |ACC Document: Additional Item Information                   |
    |ACCIT_JV                 |Joint Venture Accounting                                    |
    |ACCIT_KEY                |Key: FI/CO Line Item                                        |
    |ACCIT_WT                 |Withholding tax information for FI Interface                |
    |ACCRDF                   |Fields for Posting Small Differences: Preparation           |
    |ACC_DOCUMENT             |Accounting document                                         |
    |ACC_KONTEXT              |Context Info for FI Single Screen Transactions FB50 and FB60|
    |ACERRLOG                 |Return Parameter                                            |
    |ACGL_HEAD                |Fields for Document Header Entry Screen                     |
    |ACGL_ITEM                |Structure for Table Control: G/L Account Entry              |
    |ACSCR                    |Communication Structure for Field Modification SAPLFDCB     |
    |ACSPLT                   |Carrier for Split Information re: Current Account Line Items|
    |ACSPLT_WTNEW             |Proportion of New Withholding Tax                           |
    |ACSPLT_WTOLD             |Proportion of Old Withholding Tax                           |
    |ADDR1_SEL                |Address selection parameter                                 |
    |AEBPP_KNBK               |Additional Fields Bank Data Biller Direct                   |
    |AEBPP_LFBK               |Additional Fields Bank Data Biller Direct                   |
    |AFMIOI                   |Append for new fields ECC50/ERP                             |
    |AFMIOI_USFG              | SD order needs quantity                                    |
    |AFMISPS                  |Additional Fields for Table FMISPS                          |
    |AFM_ACCIT_EXTENSION      |Extension for FM Payment Update                             |
    |AFM_FAGL_GLT0_ACCIT_EXT  |Extension FM Account Assignments                            |
    |AFM_FI_BKPF_SUBST        |Append to Structure BKPF_SUBST                              |
    |AFM_FMFCTF               |Append for Fund Center substrings                           |
    |AFM_FMFINCODE            |Append for Fund substrings                                  |
    |AIFM01D                  |Append for IFM01D                                           |
    |AKNA1_FMFG               |US Federal Government Customer Master Data Additional Fields|
    |AKNA1_PSO                |Local Authority Additional Fields                           |
    |AKNB1_PSO                |IS-PS: Customer Master Record, Additional Data (Co.Code)    |
    |AKNBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALFA1_FMFG               |US Federal Government Vendor Master Data Additional Fields  |
    |ALFA1_PSO                |Local Authority Additional Fields (Address)                 |
    |ALFB1_FMFG               |PS fields for company code-specific master data field       |
    |ALFB1_PSO                |IS-PS: Data Appendix Vendor Master Record (Company Code)    |
    |ALFBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALVDYNP                  |ALV dialog screen fields                                    |
    |ALV_S_FCAT               |Field Catalog (for LVC and for KKBLO)                       |
    |ALV_S_FILT               |Filter Criteria (for LVC and for KKBLO)                     |
    |ALV_S_GRPL               |Group Levels (for LVC and for KKBLO)                        |
    |ALV_S_LAYO               |Layout (for LVC and for KKBLO)                              |
    |ALV_S_PCTL               |Structure for Checking Print in ALV                         |
    |ALV_S_PRNT               |Print settings (for LVC and KKBLO)                          |
    |ALV_S_QINF               |Structure for Quickinfos of Exceptions                      |
    |ALV_S_SGRP               |Field Groups (for LVC and for KKBLO)                        |
    |ALV_S_SORT               |Sort Criteria (for LVC and for KKBLO)                       |
    |ANBZ                     |Help structure for asset line item                          |
    |ANLZACCOUNT              |Additional Account Assignment Objects in Asset Accounting   |
    |ANLZACCOUNT_FKBER        |Account Assignment Objects: ANLZACCOUNT with Function Added |
    |ARC_PARAMS               |ImageLink structure                                         |
    |AT003_XBLNR2             |Append structure for US federal government                  |
    |AUSZ1                    |Clearing Table 1                                            |
    |AUSZ2                    |Clearing Table 2                                            |
    |AUSZ_CLR                 |Assign Clearing Item to Cleared Items                       |
    |AUSZ_CLR_ASGMT           |Assgt of Clrg Items - Cleared Items with Acct Assignment    |
    |AUSZ_INFO                |Open item data for clearing transactions                    |
    |AVBKPF_FMFG              |US federal                                                  |
    |AVBKPF_PSO               |IS-PS: Append Structure VBKPF for Payment Requests          |
    |AVBSEGDPSO               |IS-PS: Append Structure VBSEGD for Payment Requests         |
    |AVBSEGKPSO               |IS-PS: Append Structure VBSEGK for Payment Requests         |
    |AVIK                     |Payment Advice Header                                       |
    |AVIP                     |Payment Advice Line Item                                    |
    |BALHDR                   |Application log: log header                                 |
    |BALMT                    |Application Log: Structure for a formatted message          |
    |BAL_S_CLBK               |Application Log: Return routine definition                  |
    |BAL_S_CONT               |Application Log: Context                                    |
    |BAL_S_MSG                |Application Log: Message Data                               |
    |BAL_S_PAR                |Application Log: Parameter Name and Value                   |
    |BAL_S_PARM               |Application log: Parameters                                 |
    |BAPIASCONT               |Business Document Service: File Content ASCII               |
    |BAPIBDS01                |Business Document Service: Reference Structure for BAPIs    |
    |BAPICOMFIL               |BDS: Command File for Transport Entries                     |
    |BAPICOMPO2               |SBDS: Enhanced Component Information                        |
    |BAPICOMPO3               |SBDS: Enhanced Component Information                        |
    |BAPICOMPON               |Business Document Service: Component Table                  |
    |BAPICONNEC               |BDS: Structure for BDS Links                                |
    |BAPICONTEN               |Business Document Service: File Content                     |
    |BAPIDPROPT               |BDS: Structure for Properties                               |
    |BAPIFILES                |Business Document Services: Transfer Table for File Names   |
    |BAPIPROPER               |BDS: Structure for Properties                               |
    |BAPIPROPTL               |BDS: Structure for KPRO Properties                          |
    |BAPIQUERY                |BDS Structure for Query Table                               |
    |BAPIRELAT                |Business Document Service: Relations                        |
    |BAPIRET1                 |Return Parameter                                            |
    |BAPIRETURN               |Return Parameter                                            |
    |BAPISIGNAT               |Business Document Service: Signature Table                  |
    |BAPISRELAT               |Business Document Service: Relationship Table with Signature|
    |BAPIURI                  |Business Document Service: URI Table                        |
    |BDCMSGCOLL               |Collecting messages in the SAP System                       |
    |BDCRUN                   |Batch input: Runtime analysis                               |
    |BDIDOCSTAT               |ALE IDoc status (subset of all IDoc status fields)          |
    |BDI_SER                  |Serialization objects for one/several IDocs                 |
    |BDN_FKT                  |Business Document Navigator: Functions to be Excluded       |
    |BDWFAP_PAR               |Parameters for application function module - IDoc inbound   |
    |BDWFRETVAR               |Assignment of IDoc or document no. to method parameter      |
    |BDWF_PARAM               |Parameters for workflow methods for IDoc inbound processing |
    |BKDF                     |Document Header Supplement for Recurring Entry              |
    |BKDF_SUBST               |Process Interfaces: Substitutable fields during posting     |
    |BKORM                    |Accounting Correspondence Requests                          |
    |BKP1                     |Document Header Supplement for Update                       |
    |BKPF                     |Accounting Document Header                                  |
    |BKPFBU_ALV               |Document Overview: Display Document Headers in ALV Grid Ctrl|
    |BKPF_CARD                |Credit Card: Append for BKPF                                |
    |BKPF_LINE                |Item Category for XBKPF_TAB                                 |
    |BKPF_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BKPF_USFED               |Append structure for US federal government                  |
    |BLNTAB                   |Document Number Table for Financial Accounting              |
    |BNKA                     |Bank master record                                          |
    |BNKAAPP                  |Appendix to Table BNKA                                      |
    |BNKT                     |Conversion of temporary to internal bank keys               |
    |BOOLE                    |Boolean variable                                            |
    |BSEC                     |One-Time Account Data Document Segment                      |
    |BSEC_LINE                |Item Category for XBSEC_TAB                                 |
    |BSED                     |Bill of Exchange Fields Document Segment                    |
    |BSEE                     |Changeable Fields in the Line Item                          |
    |BSEG                     |Accounting Document Segment                                 |
    |BSEGL                    |Document Segment: Fields Derived for Line Layout Variant    |
    |BSEGS                    |G/L Item Transfer Structure for Single Screen Transactions  |
    |BSEGT                    |Transfer Table for the Tax Postings to be Generated         |
    |BSEGZ                    |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
    |BSEG_ALV                 |Document Overview: Document Item Display in ALV Grid Control|
    |BSEG_LINE                |Item Category for XBSEG_TAB                                 |
    |BSEG_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BSET                     |Tax Data Document Segment                                   |
    |BSEU                     |Line Item Additional Information (Update)                   |
    |BSEZ                     |Line Item Additional Information (Online)                   |
    |BSEZ_LINE                |Line Item Category for XBSEZ_TAB                            |
    |BSID                     |Accounting: Secondary Index for Customers                   |
    |BSIK                     |Accounting: Secondary Index for Vendors                     |
    |BSIP                     |Index for Vendor Validation of Double Documents             |
    |BSIS                     |Accounting: Secondary Index for G/L Accounts                |
    |BSIX                     |Index table for customer bills of exchange used             |
    |BTXKDF                   |Fields for Exch.Rate Difference Posting for Taxes           |
    |BVOR                     |Intercompany posting procedures                             |
    |CACS_A_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_A_CUST_COND         |Commissions: Customer Fields Condition Technique            |
    |CACS_A_FIELDSPRICING     |Append for Condition Technique Fields from Commission System|
    |CACS_S_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_S_CUST_COND         |Condition Attributes                                        |
    |CACS_S_FIELDSPRICING     |Comm.: All Condition Technique-Relevant Commission Fields   |
    |CACS_S_FSINS             |Customer Fields for Condition Technique of Insurances       |
    |CCDATA                   |Payment cards: Database fields relevant to both SD and FI   |
    |CFW_LINK                 |CFW: Link Info of a Container                               |
    |CI_COBL                  |Extension                                                   |
    |CKI_ACCIT_ML             |Transfer from MM to ML in accit-structure                   |
    |CNTLSTRLIS               |Control stream list                                         |
    |COBK                     |CO Object: Document Header                                  |
    |COBK_ONLY                |Non-key fields only in COBK (INCLUDE structure)             |
    |COBL                     |Coding Block                                                |
    |COBLF                    |Coding block: Tax table structure                           |
    |COBL_COKZ                |Assignment types for CO account assignments                 |
    |COBL_DB_INCLUDE          |Include with Additional Account Assignments for DB Tables   |
    |COBL_EX                  |Coding Block for External Applications (Not CO/FI)          |
    |COBL_FI                  |Fields from COBL that Must not Be Overwritten in FI         |
    |COBL_FM                  |Additional Fields for FM                                    |
    |D010SINF                 |Generated Table for View D010SINF                           |
    |D020S                    |System table D020S (screen sources)                         |
    |D020T                    |Screen Short Description                                    |
    |DBSEG                    |Dialog Supplementation BSEG (Taxes)                         |
    |DD02L                    |SAP Tables                                                  |
    |DD03P                    |Structure                                                   |
    |DD03V                    |Table fields view                                           |
    |DD07V                    |Generated Table for View DD07V                              |
    |DD23L                    |Matchcode ID                                                |
    |DD32P                    |Interface structure for search help parameters              |
    |DDSHDEFLT                |Description of a default value for search help fields       |
    |DDSHDESCR                |Interface: elementary search helps of a search help         |
    |DDSHFPROP                |Characteristics of search help parameters                   |
    |DDSHIFACE                |Interface description of a F4 help method                   |
    |DDSHRETVAL               |Interface Structure Search Help <-> Help System             |
    |DDSHSELOPT               |Selection options for value selection with search help      |
    |DDSUX030L                |Nametab Header, Database Structure DDNTT                    |
    |DDSUX031L                |Nametab Structure, Database Structure DDNTF                 |
    |DDTYPES                  |Table of all Dictionary types and classes                   |
    |DFIES                    |DD Interface: Table Fields for DDIF_FIELDINFO_GET           |
    |DISVARIANT               |Layout (External Use)                                       |
    |DOKHL                    |Documentation: Headers                                      |
    |DPPROPS                  |General property structure for data provider                |
    |DTC_S_LAYO               |Structure for Design of Double Table Control                |
    |DTC_S_TC                 |Structure for table controls in the double table dialog box |
    |DTC_S_TS                 |Tab Title Structure                                         |
    |DYNPREAD                 |Fields of the current screen (with values)                  |
    |E071                     |Change & Transport System: Object Entries of Requests/Tasks |
    |E071K                    |Change & Transport System: Key Entries of Requests/Tasks    |
    |EAPS_20                  |Field Enhancements for EA-PS 2.0                            |
    |EDIDC                    |Control record (IDoc)                                       |
    |EDIDS                    |Status Record (IDoc)                                        |
    |EDIFCT                   |IDoc: Assignment of FM to log. message and IDoc type        |
    |EDIMESSAGE               |Transfer Structure with all Sy Fields for T100              |
    |EDI_DS                   |Status record for interface to EDI subsystem                |
    |EDI_HELP                 |Help Structure for Reference Fields in EDI Function Groups  |
    |EK05A                    |Communication Area Purchasing - Financial Accounting        |
    |ESKN                     |Account Assignment in Service Package                       |
    |EUDB                     |Development Environment Objects                             |
    |EUOBJ                    |Workbench: Development Objects                              |
    |EXCLTAB_LINE             |Lines of EXCLTAB with OK Code to be Deactivated             |
    |EXISTING_DOC             |Original Document                                           |
    |F05ACTRL                 |Control Fields for SAPMF05A and Subprograms                 |
    |FAGLBSEGL_S              |Additional Sender Flds from General Ledger for Doc. Overview|
    |FAGL_GLT0_ACCIT_EXT      |Line Information for Document Splitting                     |
    |FAGL_MIG_S_BUKRS_LEDGER  |Combination of Company Code and Assigned Ledgers            |
    |FAGL_SPLIT_FLD_S         |Characteristics Permitted for Split                         |
    |FAGL_S_APPLICATION       |Application and Subapplication                              |
    |FAGL_S_BALDIM            |G/L Characteristics of Document Split in New General Ledger |
    |FAGL_S_BUKRS             |Structure with Company Code                                 |
    |FAGL_S_BUKRS_EXT         |Structure: Company Codes --> Ledgers                        |
    |FAGL_S_CURTYPES          |Currency Types of a Ledger                                  |
    |FAGL_S_MIG_001           |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S           |
    |FAGL_S_MIG_MGPLN_EXT     |Structure: Extended Migration Plan Information              |
    |FAGL_S_T8G40_BS          |Split Fields with Characteristic "Balance Sheet"            |
    |FCRD_VBKPF               |Credit Card: Include for Appends for BKPF, VBKPF            |
    |FCRD_VBSEG               |Include for Appends for VBSE*                               |
    |FDM_AR_CASE_ATTR_1       |FSCM DM:                                                    |
    |FDM_AR_LINE_ITEM         |FSCM: DM                                                    |
    |FDM_AR_RFPOS             |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
    |FELD                     |Screen Painter fields (internal)                            |
    |FICCO                    |Adjustment Values for External Document Items               |
    |FICCT                    |Totals Information for Interclient Posting                  |
    |FICTX                    |Tax Information for ICT                                     |
    |FIELDINFO                |Field attributes for a specific field                       |
    |FIN1_PARAM               |OBNG: Trans. structure for official doc. numbering (global) |
    |FIN1_PARAM_FI            |OBNG: FI parameters                                         |
    |FIN1_PARAM_MM            |OBNG: MM Parameters                                         |
    |FIPEX_STRUC              |Subfields Commitment Item                                   |
    |FIPOEXT                  |Help structure for line items to be generated automatically |
    |FIREVDOC                 |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS     |
    |FISTL_STRUC              |Substructure Fund Center                                    |
    |FM01                     |Financial Management Areas                                  |
    |FMBLSTRING_COMPONENTS    |Component of the BL String                                  |
    |FMCI                     |Commitment items master data                                |
    |FMDY                     |FIFM: Screen Fields                                         |
    |FMFCTR                   |Funds Center Master Record                                  |
    |FMFG_ACCIT_EXTENSION     |Extention for all fields that have to be transfered into BL |
    |FMFINCODE                |FIFM: Financing code                                        |
    |FMFPO                    |FIFM: Commitment Item                                       |
    |FMHRBA_NEG_DOC_TYPES     |HR Integration: Doc. Types for Negative Funds Commitments   |
    |FMHRBA_SETTINGS          |Integration with HR: Settings                               |
    |FMHRBA_VAD_SETTINGS      |HR Integration: Generate Value Adjustment Docs for Changes  |
    |FMICCN                   |FM: Append Structure for FMIOI (CCN Fields)                 |
    |FMIDATA                  |Common Data for Funds Management Actual Data                |
    |FMIDATAFI                |Clean FI Data for Funds Management Actual Data              |
    |FMIDATAOI                |Clean Open Item Data for Funds Management Actual Data       |
    |FMIFIIT                  |FI Line Item Table in Funds Management                      |
    |FMIKEY                   |Common Key for Funds Management Actual Data                 |
    |FMIKEYFI                 |FI - Key for Funds Management Actual Data                   |
    |FMIKEYOI                 |Common Key for Funds Management Actual Data                 |
    |FMIOI                    |Commitment Documents Funds Management                       |
    |FMIOIKEY                 |Key for Table FMIOI                                         |
    |FMIOI_USFG               | SD order needs quantity                                    |
    |FMIREF                   |Ref. Funds Management Actual Data to Preceding Document     |
    |FMISPS                   |General Parameters for Funds Management                     |
    |FMIT                     |Totals Table for Funds Management                           |
    |FMMRESERV                |Include for the Reduction of Funds Reservations (FM)        |
    |FMRFC                    |Function Modules and their RFC Destinations                 |
    |FMSP_SPLIT_FIELDS        |PSM Fields used in multiple account splitting               |
    |FMT001                   |Additional Customizing for Funds Management                 |
    |FMUP00T                  |Update Profiles                                             |
    |FMUP01                   |Update Control with Value Type Dependency                   |
    |FMUP_INV_KEY             |Extension for FM Update: FI Key of Invoice                  |
    |FMUP_PAY_KEY             |Extension for FM Update: FI Key of Payment                  |
    |FS006                    |Fields for Optical Archiving                                |
    |FTCHECK                  |Foreign Trade: Import Simulation - Ctrl Fields for Pricing  |
    |FTEXTS                   |Communication Structure for Additional Components           |
    |FTGENERAL                |Foreign Trade: General Fields Item                          |
    |FUND_STRUC               |Substructure Fonds                                          |
    |FVD_TZB0A                |Append to TZBOA: Loans Fields                               |
    |GLACCOUNT_CCODE          |G/L Account Master Record: Company Code                     |
    |GLACCOUNT_CCODE_DATA     |G/L Account Master Record: Company Code - Data              |
    |GLACCOUNT_CCODE_INFO     |G/L Account Master Record: Company Code - Information       |
    |GLACCOUNT_CCODE_KEY      |G/L Account Master Record: Company Code - Key               |
    |GLX_ORG_INFO             |Organizational Assignment                                   |
    |GMBSEGZ                  |Grants Management Add-on                                    |
    |GXXLT_H                  |XXL interface: horizontal features                          |
    |GXXLT_O                  |XXL_interface: texts for online display                     |
    |GXXLT_S                  |XXL interface: structure of the semantics table             |
    |GXXLT_V                  |XXL interface: vertical features                            |
    |HELPVAL                  |Restrict Value Range - Transfer Table                       |
    |HELP_INFO                |Transfer Values for the Help Processor                      |
    |HELP_VALUE               |Structure or Function Module HELP_VALUE_GET_FOR_TABLE       |
    |HHM_COBL                 |Include for COBL from FM                                    |
    |IADDR_PSO                |Local Authority Additional Fields (Address)                 |
    |IBKPF_PSO                |IS-PS: Include Structure BKPF Payment Request Doc.Header    |
    |ICDIND                   |Structures for generating change document update programs   |
    |ICON                     |Icons table                                                 |
    |ICONS                    |Icons                                                       |
    |ICURR                    |Interface for Currency Translation                  

  • Smartform for SUS PO

    Hi,
    I am trying to modify the smartform for SUS PO - BBP_SUSPO.
    I want to change the SAP logo which appears in the smartform. If I have to adopt a different custom logo, where do I need to define this?
    Also, once I create the ZBBP_SUSPO with the changes, where to define it in spro?
    I checked SRM Server> Cross application settings>Set output actions and output format-->Define actions for document output, but this only has action profiles for EBP PO (BBP_PD_PO).
    Where to define the smartform for SUS PO print?
    Thanks & regards,
    Srivatsan

    Hi
    <b>The smart form name is BBP_SUSPO. This is correct in your case.</b>
    <u>Refer to following SAP OSS Notes -></u>
    Note 1001986 - SRM50: Schedule lines incorrect in smartform BBP_SUSPO
    Note 925678 Backend Purchase Order in SUS 3.0 Print.
    Note 791623 SRM4.0/SUS/SMARTFORMS: Corrections of SP05
    890252 Delivery/Ship to Address is shown wrong on print of Order
    Note 823893 SRM archiving: Archiving workflow items
    814520 SRM archiving: Table BBP_PDBGP for BBP_SUSPO Aobj is missing
    Note 786239 SUS: Print of documents dumps
    <u>Few BADIs which might help -></u>
    BAdI Definition Name Description                                                                               
    BBP_SUS_BP_DUPLCHECK SUS/BP Enhancement for Finding Duplicate Records              
    BBP_SUS_BP_TAXNUMMAP Enhancement for Mapping Tax Number                            
    BBP_SUS_DOWNLD_FILES SUS: Download Documents as Files                              
    BBP_SUS_FILTER_SCHAR Filter Scheduling Agreements                                  
    BBP_SUS_MAIL_DESCR   Change Subject Field Text for E-Mail Notification in SUS      
    BBP_SUS_QUAN_PROPOSE Propose Quantities for Service Items                                                                               
    Incase this does not help, we can go for some BADI implemenatation to get this done.
    Do let me know.
    Regards
    - Atul

  • [Error ORABPEL - 10900]... : Can not find definition for element 'process'

    Hi,
    When I try to deploy a bpel process using JDeveloper I'm having the following xml parse error:
    Error(21):
    [Error ORABPEL-10900]: xml parser error
    [Description]: in line 21 of "file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel", XML parsing failed because file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel<Line 21, Column 63>: XML-24538: (Error) Can not find definition for element 'process'.
    [Potential fix]: Fix the invalid XML.
    I don't understand why... Any idea?

    Ok.
    This is my BPEL code. The sapattern tags are from a program that is generating part of the code. The JDeveloper doesn't show any error, I only get the error when I try to deploy.
    <?xml version = "1.0" encoding = "UTF-8" ?>
    <process name="CriarProjectoSA"
    targetNamespace="http://xmlns.oracle.com/CriarProjectoSA"
    suppressJoinFailure="no"
    xmlns="http://xmlns.oracle.com/CriarProjectoSA"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:ns4="http://xmlns.oracle.com/CriarProjectoSA"
    xmlns:ns7="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns5="http://schemas.oracle.com/xpath/extension"
    xmlns:ns6="http://xmlns.oracle.com/bpel/workflow/xpath"
    xmlns:ns11="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
    xmlns:ns9="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
    xmlns:ns1="http://xmlns.oracle.com/ValidacaoProjectos"
    xmlns:ns3="http://www.nerga.pt" xmlns:ns2="http://tempuri.org/"
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    xmlns:ns10="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
    xmlns:ns8="http://schemas.xmlsoap.org/ws/2003/03/business-process/">
    <!--Generated by Telelogic System Architect on 05/01/2007 11:06:18 by easm-->
    <sapattern>
    <guid>41207640-d934-480f-902a-b3764f3d9c9f</guid>
    </sapattern>
    <partnerLinks>
    <partnerLink name="client" partnerLinkType="ns4:CriarProjectoSA"
    myRole="CriarProjectoSAProvider"/>
    <partnerLink name="NergaIS" partnerLinkType="ns2:ServiceSoap_PL"
    myRole="ServiceSoap_Role" partnerRole="ServiceSoap_Role"/>
    <partnerLink name="ValidacaoProjectos"
    partnerLinkType="ns1:ValidacaoProjectos"
    myRole="ValidacaoProjectosRequester"
    partnerRole="ValidacaoProjectosProvider"/>
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
    <guid>3111d1af-0b31-4d02-b3fc-73d14ce95405</guid>
    <guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
    </sapattern>
    </partnerLinks>
    <variables>
    <variable name="outputVariable"
    messageType="ns4:CriarProjectoSAResponseMessage"/>
    <variable name="inputVariable"
    messageType="ns4:CriarProjectoSARequestMessage"/>
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>2503e820-3add-4cd1-bbc5-5cc5fff57090</guid>
    <guid>8bcc3532-46b7-4e88-816f-72ecdaee76ab</guid>
    </sapattern>
    <variable name="invocaVP_initiate_InputVariable"
    messageType="ns1:ValidacaoProjectosRequestMessage"/>
    <variable name="recebeVP_onResult_InputVariable"
    messageType="ns1:ValidacaoProjectosResponseMessage"/>
    <variable name="InvocaAdicionarProjecto_InputVariable"
    messageType="ns2:AdicionarProjectoSoapIn"/>
    <variable name="InvocaAdicionarProjecto_OutputVariable"
    messageType="ns2:AdicionarProjectoSoapOut"/>
    </variables>
    <sequence>
    <receive name="recebeTemplate" joinCondition="False" partnerLink="client"
    portType="ns4:CriarProjectoSA" operation="process"
    variable="inputVariable" createInstance="yes">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
    <guid>68e62379-55ac-48eb-b681-aee8f5a7696d</guid>
    </sapattern>
    </receive>
    <scope variableAccessSerializable="no" name="ValidarExigências"
    joinCondition="False">
    <faultHandlers>
    <catchAll>
    <assign name="assignInvalid">
    <bpelx:append>
    <bpelx:from expression="concat(ns8:getVariableData('inputVariable','payload','/ns3:Template/ns3:Projecto/ns3:Observacoes'), string('Projecto inválido!!'))"/>
    <bpelx:to variable="inputVariable" part="payload"
    query="/ns3:Template/ns3:Projecto/ns3:Observacoes"/>
    </bpelx:append>
    </assign>
    </catchAll>
    </faultHandlers>
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
    </sapattern>
    <sequence name="ValidarExigências" joinCondition="False">
    <assign name="assignVPIn">
    <copy>
    <from variable="inputVariable" part="payload"/>
    <to variable="invocaVP_initiate_InputVariable" part="payload"/>
    </copy>
    </assign>
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
    </sapattern>
    <invoke name="invocaVP" joinCondition="False"
    partnerLink="ValidacaoProjectos" portType="ns1:ValidacaoProjectos"
    operation="initiate"
    inputVariable="invocaVP_initiate_InputVariable">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>f3bc9c04-f4d2-4e96-acc8-7a6c88a8ced5</guid>
    </sapattern>
    </invoke>
    <receive name="recebeVP" joinCondition="False"
    partnerLink="ValidacaoProjectos"
    portType="ns1:ValidacaoProjectosCallback" operation="onResult"
    createInstance="no" variable="recebeVP_onResult_InputVariable">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
    <guid>1eba96a8-330a-4e4d-a14b-cdf6641fa614</guid>
    </sapattern>
    </receive>
    <assign name="assignVPOut">
    <copy>
    <from variable="recebeVP_onResult_InputVariable" part="payload"/>
    <to variable="inputVariable" part="payload"/>
    </copy>
    </assign>
    </sequence>
    </scope>
    <scope variableAccessSerializable="no" name="AdicionarProjecto"
    joinCondition="False">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
    </sapattern>
    <sequence name="InvocarISAdicionarProjecto" joinCondition="False">
    <assign name="assignIS">
    <copy>
    <from variable="inputVariable" part="payload"
    query="/ns3:Template/ns3:Projecto/ns3:NomeProjecto"/>
    <to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
    query="/ns2:AdicionarProjecto/ns2:nome"/>
    </copy>
    <copy>
    <from variable="inputVariable" part="payload"
    query="/ns3:Template/ns3:Projecto/ns3:TipoProjecto"/>
    <to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
    query="/ns2:AdicionarProjecto/ns2:tipo"/>
    </copy>
    </assign>
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
    </sapattern>
    <invoke name="InvocaAdicionarProjecto" joinCondition="False"
    partnerLink="NergaIS" portType="ns2:ServiceSoap"
    operation="AdicionarProjecto"
    inputVariable="InvocaAdicionarProjecto_InputVariable"
    outputVariable="InvocaAdicionarProjecto_OutputVariable">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>76519bd3-c506-4c79-8190-8ff09abdd27d</guid>
    </sapattern>
    </invoke>
    </sequence>
    </scope>
    <assign name="assignOutput">
    <copy>
    <from variable="inputVariable" part="payload"
    query="/ns3:Template/ns3:Projecto"/>
    <to variable="outputVariable" part="payload"/>
    </copy>
    </assign>
    <reply name="devolveProjecto" joinCondition="False" partnerLink="client"
    portType="ns4:CriarProjectoSA" operation="process"
    variable="outputVariable">
    <sapattern>
    <!--The System Architect objects used in the pattern. To ensure traceability to System Architect DO NOT REMOVE-->
    <guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
    <guid>0dbefef0-3d04-4356-abbc-b291ea40d256</guid>
    </sapattern>
    </reply>
    </sequence>
    </process>

Maybe you are looking for

  • Timewarp / time remapping not running smoothly?

    Hi, I've got a problem with speed variation. I got 25fps exr footage rendered out of 3ds max which I want to add some speed variation to it in AE. The problem I'm facing is the footage stutters when using time remapping. basically what I was trying t

  • FD32 Credit management 'sales value'

    I am on SAP ERP, I'm trying to figure out how to pull the data that makes up the credit exposure - 'SALES VALUE.'  I believe the sale value includes all undelivered or only partially delivered orders.  I can not find a way to confirm what makes up th

  • Writing files from applet

    We ran into a problem with our Applet. We need to produce a report (it is prefferable to save it as a text file or HTML). We tried to use DataOuputStream to write out to a text file. It works on a local machine but we get a security exception when ap

  • Send Report to printer

    Hi, Windows Xp, Oracle`10g, Oracle Db g. I am Try to send a report direct to printer . I add parameter DesType = Printer, DesName = Printer Name But nothing happen no errors nothing happen. What is the problem? Regards,

  • Will lightroom 4.4. recognize nikon d810 raw files

    Will lightroom 4.4 import Nikon d810 raw files. Rick