TRM Correspondence Definition

Hi Experts:
I have customized the correspondence so that any time a transaction is settle it prints a documents or send an email. In this case the documents has payments details and the structure of the transaction.
But if the transaction has a decrease in the amount due to a previous payment of the principal and or the interest or a new other flow, how do I get the correspondence of those specific flows (i.e in money market a 1110 Decrease 1200 payed untill due date or a 5001 other flow axes)
thanks in advance
Regards
Claudio

Hi,
I guess you are using the old correspondence feature and not the correspondence framework which is available from EH3 onwards.  Anyway for your case, you can define a new correspondence type for printing and assign that for a new activity for your product type. 
You can specify the last function as change and the activity category as contract or settlement as per your requirement. You can check the form F_TR_CONFIRM_ALL or F_TR_DEALER_ALL which is a dealing slip.  These forms would contain the flows.  But in case if this is not suffecient, you can develop a new form and assign it for this activity.
Regards,
Ravi

Similar Messages

  • TRM Correspondence Type Definition (config) and Automatic Creation

    I am on ECC 6.0 EHP4, and attempting to follow configuration instructions provided by SAP related to defining and setting up correspondence types to ensure automatic generation. I'm trying to find the setting described in the below statement:
    "4. You also specify here whether correspondence should be generated automatically for each correspondence activity. Automatically means that the planned record for correspondence is immediately carried out when you save the correspondence-relevant activity.  If you do not set this indicator, when you save the correspondence-relevant activity, the planned record for correspondence is saved. Correspondence is then generated via the report entitled 'Outgoing correspondence'."
    The above statement is from this link:
    [http://help.sap.com/erp2005_ehp_04/helpdata/EN/d2/6f73c5415e11d182b10000e829fbfe/frameset.htm]
    Does anyone know if the setting for automatic generation of correspondence is added from application of an OSS note or through programming a badi? I haven't been able to find the setting for automatic generation of correspondence.
    Brian

    Hello,
    In the Implementation Guide for the Transaction Manager by choosing Money Market/Foreign Exchange/Securities/Listed Derivatives/OTC Derivatives  -> Transaction Management  -> Correspondence  -> Define Correspondence Activities,
    you will see an indicator AutoCorr (AUTOMATIC):
    Indicator: Automatic Correspondence Required?
    The indicator shows that correspondence is to be produced automatically. Automatic correspondence is carried out when you save the transaction (i.e. the planned record created is immediately executed).
    If you need automatic generation, please set it as ON.
    Best regards,
    Jasmine

  • SAP TRM Correspondence monitor

    Hi All,
    I have a requirement for developing correspondence monitor integrating to SWIFT network, as I understood SAP EHP5 provide Correspondence monitor as standard our requirement is how to integrate SWIFT network to SAP. If any one worked on this requirement please provide some information how to integrate this to SAP from technical and functional perspective.
    SAP standard support this messages in standard 
    MT300 Foreign Exchange Confirmation
    MT320 Fixed Loan/Deposit Confirmation
    MT395 Queries
    MT399 Free Format Message
    MT502 Order to Buy/Sell
    MT509 Trade Status Message
    MT515 Confirmation of Purchase/Sale
    MT535 Statement of Holdings
    MT536 Statement of Transactions
    MT540 Receive Free
    MT541 Receive against Payment
    MT542 Deliver Free
    MT543 Deliver against Payment
    MT544 Receive Free Confirmation
    MT545 Receive against Payment Confirmation
    MT546 Deliver Free Confirmation
    MT547 Deliver against Payment Confirmation
    MT548 Settlement Status and Processing Advice
    MT566 Corporate Action Confirmation
    Regards,
    Naresh Garla.

    Hi Christoph,
    We are planning to use Correspondence Monitor. We are connected to SWIFT Network through our SWIFT Bureau.
    We have configured the SAP Transaction Manager system to generate the MT300/MT320 message as soon as the transaction is created and the MT message is sent to the counter party.
    How do we map the incoming counter confirmation (coming from the counter party) MT300/MT320  to the outgoing correspondence object and match the details and confirm the deal?
    We have licence for the SWIFT Integration package and I am not sure how it will help in updating the status in correspondence monitor.
    Appreciate your help.
    Kalyan

  • LE-TRM: Definition of host

    Dear all,
    The term of "HOST" is sometimes used in the documentation of LE-TRM module:
    - Static entity HOST of the priority model at task selection
    - HOST confirmation problem with a task selected by resource but which cannot be confirmed at final destination
    I would say that the HOST term reprensents the WM transfer order from which the task orginate from, but I'm not sure at all...
    Would you know more about it, could you please explain what exactly does the HOST term represent in LE-TRM ?
    Thx a lot in advance.
    Cheers,
    Alex

    Hi Alex,
    You have interprited this correctly it is the source or host document.
    SAP help defines it as
    " Reflects the importance of the originating instruction from the host vis-a-vis other host instructions"
    or
    "An instruction from transfer order A may be given a higher priority than an instruction from transfer order B"
    Thanks James

  • Unable to see Messages in External Definitions

    I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
    I also cannot see any messages in External Definitions.
    Can anyone help with a solution?
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
         <types>
              <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
                   <!-- address type enum -->
                   <xs:simpleType name="AddressType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="fax"/>
                             <xs:enumeration value="internet"/>
                             <xs:enumeration value="mbox"/>
                             <xs:enumeration value="x400"/>
                             <xs:enumeration value="telex"/>
                             <xs:enumeration value="cablegram"/>
                             <xs:enumeration value="mailgram"/>
                             <xs:enumeration value="ddd"/>
                             <xs:enumeration value="dedLine"/>
                             <xs:enumeration value="softswitch"/>
                             <xs:enumeration value="voice"/>
                             <xs:enumeration value="sms"/>
                             <xs:enumeration value="fod"/>
                             <xs:enumeration value="list"/>
                             <xs:enumeration value="smQuery"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!--includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="AuthenticateRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="Domain" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
                   <xs:element name="AuthenticateResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSCreateDirRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSCreateDirResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSDeleteRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDeleteResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSDownloadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDownloadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSListRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:simpleType name="EntryType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="file"/>
                             <xs:enumeration value="directory"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:element name="CFSListResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
                                       <xs:annotation>
                                            <xs:documentation>content of
                                        DirectoryEntry is path relative to
                                        the RelativePath</xs:documentation>
                                       </xs:annotation>
                                  </xs:element>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:complexType name="DirectoryEntryType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:EntryType" use="required"/>
                                  <xs:attribute name="modified" type="xs:dateTime" use="optional"/>
                                  <xs:attribute name="size" type="xs:integer" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSRenameRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="OldRelativePath" type="xs:string"/>
                                  <xs:element name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSRenameResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSUploadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSUploadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- ===============================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="EncodableStringType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         =============================== -->
                   <!-- Type definitions -->
                   <!-- Phone element -->
                   <xs:element name="Phone">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Email element -->
                   <xs:element name="Email">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:minLength value="2"/>
                                  <!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Eformat type -->
                   <xs:simpleType name="EformatType">
                        <xs:annotation>
                             <xs:documentation>      Only used in messageREACH.
                            Indicates the preferred email      format of the
                            message body the recipient will      receive.
                            Leaving the field empty or setting it to
                            "default" will send a multipart message body
                            rather than      just a single message body if
                            it would do so normally.   </xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="html"/>
                             <xs:enumeration value="htmllite"/>
                             <xs:enumeration value="default"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- insert list element -->
                   <xs:element name="InsertList">
                        <xs:complexType>
                             <xs:choice>
                                  <xs:element maxOccurs="unbounded" name="Insert">
                                       <xs:complexType>
                                            <xs:simpleContent>
                                                 <xs:extension base="xs:string">
                                                      <xs:attribute name="number" type="xs:integer"/>
                                                      <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                                 </xs:extension>
                                            </xs:simpleContent>
                                       </xs:complexType>
                                  </xs:element>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- extension element -->
                   <xs:complexType name="SegmentType">
                        <xs:choice>
                             <xs:element maxOccurs="unbounded" name="Property">
                                  <xs:complexType>
                                       <xs:simpleContent>
                                            <xs:extension base="xs:string">
                                                 <xs:attribute name="name" type="xs:string"/>
                                                 <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                            </xs:extension>
                                       </xs:simpleContent>
                                  </xs:complexType>
                             </xs:element>
                        </xs:choice>
                        <xs:attribute name="name" type="xs:string"/>
                   </xs:complexType>
                   <xs:element name="Extension">
                        <xs:complexType>
                             <xs:choice maxOccurs="unbounded">
                                  <xs:element name="Segment" type="xoa:SegmentType"/>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- field mapping type -->
                   <xs:complexType name="FieldMappingType">
                        <xs:annotation>
                             <xs:documentation>      Describes the correspondence
                            between the segment/keyword      pairs in the
                            XDDS header file and columns in a table. Only
                            two table formats currently supported: CSV
                            (comma-separated values) and XSL (Excel
                            spreadsheet).       The mapping may go either
                            from field name to the      segment/keyword pair
                            or vice versa. In both cases, the      same
                            structure may be used.   </xs:documentation>
                        </xs:annotation>
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" name="Map">
                                  <xs:complexType>
                                       <xs:sequence>
                                            <xs:element name="FieldName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
                                            <xs:element name="PropertyName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
                                       </xs:sequence>
                                  </xs:complexType>
                             </xs:element>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- class definitions -->
                   <!-- delivery item base class -->
                   <xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
                   <xs:complexType abstract="true" name="DeliveryItemType">
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                        <xs:attribute name="refb64" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item container class -->
                   <xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
                   <xs:complexType abstract="true" name="DeliveryItemContainerType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType"/>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- list delivery item class -->
                   <xs:element name="List" type="xoa:ListType"/>
                   <xs:complexType name="ListType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SmQuery delivery item class -->
                   <xs:element name="SmQuery" type="xoa:SmQueryType"/>
                   <xs:complexType name="SmQueryType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- External table delivery item class -->
                   <!-- This includes CSV and XLS files -->
                   <xs:element name="Table" type="xoa:TableType"/>
                   <xs:complexType name="TableType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
                                       <xs:choice>
                                            <xs:element name="DocRef" type="xs:string"/>
                                            <xs:element name="Document" type="xoa:DocumentType"/>
                                       </xs:choice>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item simple class -->
                   <xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
                   <xs:complexType abstract="true" name="DeliveryItemSimpleType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="Alternate">
                                            <xs:complexType>
                                                 <xs:choice>
                                                      <xs:element ref="xoa:Fax"/>
                                                      <xs:element ref="xoa:Internet"/>
                                                      <xs:element ref="xoa:Voice"/>
                                                      <xs:element ref="xoa:Fod"/>
                                                      <xs:element ref="xoa:Mbox"/>
                                                      <xs:element ref="xoa:Sms"/>
                                                      <xs:element ref="xoa:Telex"/>
                                                      <xs:element ref="xoa:DeliveryItemGeneric"/>
                                                 </xs:choice>
                                            </xs:complexType>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- mbox delivery item class -->
                   <xs:element name="Mbox" type="xoa:MboxType"/>
                   <xs:complexType name="MboxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="UserId" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- telex delivery item class -->
                   <xs:element name="Telex" type="xoa:TelexType"/>
                   <xs:complexType name="TelexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Number" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- FOD delivery item class -->
                   <xs:element name="Fod" type="xoa:FodType"/>
                   <xs:complexType name="FodType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SMS delivery item class -->
                   <xs:element name="Sms" type="xoa:SmsType"/>
                   <xs:complexType name="SmsType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- Complex delivery item class -->
                   <xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
                   <xs:complexType abstract="true" name="DeliveryItemComplexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" ref="xoa:InsertList"/>
                                       <xs:element minOccurs="0" ref="xoa:Extension"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="Fax" type="xoa:FaxType"/>
                   <xs:complexType name="FaxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                       <xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Salutation" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- voice delivery item class -->
                   <xs:element name="Voice" type="xoa:VoiceType"/>
                   <xs:complexType name="VoiceType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- internet delivery item class -->
                   <xs:element name="Internet" type="xoa:InternetType"/>
                   <xs:complexType name="InternetType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Email"/>
                                       <xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
                                       <xs:element minOccurs="0" name="Password" type="xs:string">
                                            <xs:annotation>
                                                 <xs:documentation>    Only used in
                                        messageREACH. The password used
                                        by this recipient to retrieve
                                        pull    attachments.        </xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
                   <xs:complexType name="DeliveryItemGenericType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="type" type="xoa:AddressType" use="required"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- Finally, delivery item list -->
                   <!-- delivery item list type -->
                   <xs:complexType name="DeliveryItemListType">
                        <xs:choice maxOccurs="unbounded">
                             <xs:element ref="xoa:List"/>
                             <xs:element ref="xoa:SmQuery"/>
                             <xs:element ref="xoa:Table"/>
                             <xs:element ref="xoa:DeliveryItemGeneric"/>
                             <xs:element ref="xoa:Fax"/>
                             <xs:element ref="xoa:Internet"/>
                             <xs:element ref="xoa:Voice"/>
                             <xs:element ref="xoa:Fod"/>
                             <xs:element ref="xoa:Mbox"/>
                             <xs:element ref="xoa:Sms"/>
                             <xs:element ref="xoa:Telex"/>
                        </xs:choice>
                   </xs:complexType>
                   <!--remove includes later
         <xs:include schemaLocation="AddressType.xsd"/>
         ================ -->
                   <xs:complexType name="DestinationType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:AddressType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- ===============================
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         =============================== -->
                   <!-- Elementary definitions go first -->
                   <xs:element name="CharacterSet" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>use ISO names</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <!-- Document type -->
                   <xs:simpleType name="DocFormatType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="XMF"/>
                             <xs:enumeration value="TIFF"/>
                             <xs:enumeration value="XAR"/>
                             <xs:enumeration value="PS"/>
                             <xs:enumeration value="PCL"/>
                             <xs:enumeration value="PDF"/>
                             <xs:enumeration value="MSW"/>
                             <xs:enumeration value="WAV"/>
                             <xs:enumeration value="RTF"/>
                             <xs:enumeration value="XLS"/>
                             <xs:enumeration value="HTML"/>
                             <xs:enumeration value="HTMLLITE"/>
                             <xs:enumeration value="unspec"/>
                             <xs:enumeration value="GIF"/>
                             <xs:enumeration value="JPEG"/>
                             <xs:enumeration value="PPT"/>
                             <xs:enumeration value="BMP"/>
                             <xs:enumeration value="VSD"/>
                             <xs:enumeration value="PUB"/>
                             <xs:enumeration value="MPP"/>
                             <xs:enumeration value="empty"/>
                             <!-- We do not need to know the document type for the -->
                             <!-- email attachments. -->
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document Encoding format -->
                   <xs:simpleType name="DocEncodingFormat">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="base64"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document embedded into the request -->
                   <xs:complexType name="DocDataType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- All supported stored object types -->
                   <xs:simpleType name="SosObjectType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="tts"/>
                             <xs:enumeration value="vcs"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- The types of the sos stored objects -->
                   <xs:complexType name="SosObjectIdType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- Another Document type -->
                   <xs:complexType name="DocumentType">
                        <xs:sequence>
                             <xs:element name="DocType" type="xoa:DocFormatType"/>
                             <xs:element minOccurs="0" name="Filename" type="xs:string"/>
                             <xs:choice>
                                  <xs:element name="DocData" type="xoa:DocDataType"/>
                                  <xs:element name="DocCfs" type="xs:string"/>
                                  <xs:element name="DocUrl" type="xs:anyURI"/>
                                  <xs:element name="SosObject" type="xoa:SosObjectIdType"/>
                             </xs:choice>
                             <xs:element minOccurs="0" ref="xoa:CharacterSet"/>
                        </xs:sequence>
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- The document set type -->
                   <xs:complexType name="DocumentSetType">
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- The document by value or by reference -->
                   <xs:complexType name="DocumentOrRefType">
                        <xs:choice>
                             <xs:element name="DocRef" type="xs:string">
                                  <xs:annotation>
                                       <xs:documentation>must refer to a document
                                    in document_set</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element name="Document" type="xoa:DocumentType"/>
                        </xs:choice>
                   </xs:complexType>
                   <xs:complexType name="EncodableStringType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!--includes for standalone validation
         ================ -->
                   <xs:simpleType name="HistoryActionType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="inserted"/>
                             <xs:enumeration value="updated"/>
                             <xs:enumeration value="deleted"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="ItemCountType">
                        <xs:simpleContent>
                             <xs:extension base="xs:integer">
                                  <xs:attribute name="type" type="xoa:HistoryActionType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <xs:complexType name="HistoryType">
                        <xs:sequence>
                             <xs:element name="Action" type="xs:string"/>
                             <xs:element name="Operator" type="xs:string"/>
                             <xs:element name="Agent" type="xs:string"/>
                             <xs:element name="Time" type="xs:dateTime"/>
                             <xs:element name="ItemCount" type="xoa:ItemCountType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- ================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="DestinationType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="JobIdType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="RecStatusType.xsd"/>
         ================ -->
                   <xs:simpleType name="JobCancelType">
                        <xs:annotation>
                             <xs:documentation>The set of cancellation types/options</xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="All"/>
                             <xs:enumeration value="Deliveries"/>
                             <xs:enumeration value="Reports"/>
                             <xs:enumeration value="AcceptanceReport"/>
                             <xs:enumeration value="CancellationNotice"/>
                             <xs:enumeration value="Pulls"/>
                             <xs:enumeration value="FriendDeliveries"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="JobCancelItemType">
                        <xs:sequence>
                             <xs:element name="JobId" type="xoa:JobIdType">
                                  <xs:annotation>
                                       <xs:documentation>requested JobId</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
                             <xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
                             <xs:choice minOccurs="0">
                                  <xs:element name="NotificationType" type="xs:string"/>
                                  <xs:element name="NotificationText" type="xoa:DocDataType"/>
                             </xs:choice>
                        </xs:sequence>
                   </xs:complexType>
                   &

    Hi,
    Not all data types from WSDL are supported during import. There is SAP Note about it.
    please read it:
    /people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
    regards,
    wojtek
    Message was edited by: Wojciech Gasiorowski

  • How do I completely enable a new custom asset in Correspondence Management?

    Hello!
    I'm trying to add a new custom asset to the Correspondence Management Solution Accelerator, and have it behave like all other assets in the system (ie searchable, updateable etc).  I'm almost there, but there's obviously something I'm missing, and I was hoping someone here might have done this before, or have a link to some documentation regarding the matter that I may have missed.  The asset I'm trying finish creating is for a LiveCycle user in a specific domain.  This is what I've done so far...
    I've created the asset definition MyUser.fml and placed it in the FSIApp\Portal\webapp\WEB-INF\assetDefinitions folder.  I've then registered this fml file in the spring-config.xml file in both the 'lc.cm.assetDefinitionsDeployer' and 'lc.cm.assetTypeRegistryBootstrapper' beans.  In the 'lc.cm.assetTypeRegistryBootstrapper' bean, I set the key to 'MyUser', and the value to the class path of my Java class that represents this asset.
    On the Java side I've created the MyUser.java class, as well as MyUserService.java and MyUserServiceImpl.java to allow the searching, updating etc of the MyUser assets.
    After running the Bootstrap process, I can log into the Manage Templates application, select Data Dictionaries from the 'View' dropdown, and view/edit the MyUser data dictionary properties with no problems.  So I'm happy that the asset has successfully been registered with the application.
    Where I'm stuck is choosing the MyUser asset from the drop down, and searching the system for assets of that type.  I can choose the MyUser asset type from the 'view' drop down, but the search result returns an empty array.
    From digging into the existing Manage Templates code, I've created the following classes:
    public interface IMyUserService extends IEventDispatcher -  containing the following function definitions:
              function getMyUser(id:String):IAsyncToken;
              function getAllMyUsers(param1:Query=null):IAsyncToken;
    public class MyUserSeviceProvider extends ServiceProvider - containing a getter/setter for MyUserServiceDelegate
    public class MyUserServiceDelegate extends ServiceDelegate implements IMyUserService - containing the functions defined in IMyUserService, as well as creating the RemoteObject to perform the actions.
    The MyUserServiceDelegate constructor is:
         public function MyUserServiceDelegate ()
                super();
                _service = new RemoteObject("myapplication.services.myUserService");
                _service.showBusyCursor = true;
    This is the code for the function in getAllMyUsers in MyUserServiceDelegate:
         public function getAllMyUsers(param1:Query = null):IAsyncToken
                var operationToken:AsyncToken = this._service.getAllMyUsers(param1);
                var token:IccToken = new IccToken(this.className + ".getAllMyUsers");
                operationToken.addResponder(getDefaultResponder(token));
                return token;
    I've also made changes to the following config files to register the RemoteObject destination specified in the MyUserServiceDelegate constructor:
    spring-http-config.xml:
         <bean name="/service/UserService" class="org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter">
            <property name="service" ref="myapplication.services.myUserService" />
            <property name="serviceInterface" value="com.mydomain.lc.services.MyUserService" />
        </bean>
    remoting-config.xml:
         <destination id="myapplication.services.myUserService"/>
    flexmessagebroker-servlet.xml
         <flex:remoting-destination ref="myapplication.services.myUserService" />
    Above my Java class definition of MyUserServiceImpl.java I have the following line:
    @Service("myapplication.services.myUserService")
    So......
    My problem is that when I choose the MyUser asset from the drop down, no search results are returned (an empty array is returned).  I have logging code in the getAllMyUsers function in the MyUserServiceDelegateclass.as, as well as logging in the MyUserServiceImpl.java class (not shown in the above code snippets) and neither of them fire when selecting the MyUser asset from the drop down.  So neither of the classes are being called on the search.  If I force a search via the following line:
    MyUserSeviceProvider.getMyUserService().getAllMyUsers();
    the logging in both the Flex and Java classes works (and the java class returns the results as expected).  So I'm happy that these functions, as well as the linking between the Flex and the Java side is working correctly.
    The step that I can't seem to work out is having the selection of the asset in the drop down call the desired function automagically.  I've been digging into the SearchManager, the ServiceLocator and heaps of other classes, but I'm falling deeper and deeper into the rabbit hole...
    Can anyone shed some light on what they think might be needed to make the final link here?  I've been digging and digging into the code for days now and my brain hurts!!
    Any advice appreciated!!
    Thanks,
    Kristian

    Hi Saket,
    By 'not really complete' I'm assuming (hoping) that some work has been done on this already.  Our project requires the use of custom assets, so it's very important that we get this functionality running as soon as possible.
    Any help, unsupported or otherwise, would be great.  Feel free to email me any details if you'd prefer not to post anything public on the boards.
    Cheers,
    Kristian

  • TRM accounting configuration needed to switch from F111 to F110

    I had all TRM configuration done for working with F111. Now my customer wants to use F110 instead of F111, paying via customers instead of gl accounts. F110 was already working for FI-AP and AR.
    What do I have to do in TRM customizing and master data?  I  assigned already an existing FI-AR customer to existing Financial Services/Counterparty business partner via FLBPD1 transaction. I suppose in 'Account Determination' I have to maintain 'Definition of posting specifications' and 'assignment of update types to posting specifications'. But what do I have to there? change or create additional records? In  'assignment of update types to posting specifications' should I copy the original update types, check mark the field 'payment transaction' and assign an posting spec that relates to subledger postings (posting category 2 'sub ledger posting in payment currency')?
    In FTR_CREATE in tabpage payment details I check marked 'posting to customer', house bank and account id filled out, payer/payee filled with business partner number that was assigned to customer, payment method that works for FI-AP, partner bank filled out.

    Hi thanks, I only have to create new posting specifications for the Position Posting Specifications? In the new ones I replace bank by customer?
    11000     - - - - - - - - - - P O S I T I O N - - - - - - - - - - - -
    11100     Position to Bank Clearing
    11110     Interest Payables to Bank Clearing
    11200     Bank Clearing to Position
    11210     Bank Clearing to Interest Receivable
    11300     Position to Position Clearing
    11310     Asset Position to Position Clearing (Derivatives)
    11320     Liab. Position to Position Clearing (Derivatives)
    11400     Position Clearing to Position
    11410     Position Clearing to Asset Position (Derivatives)
    11420     Position Clearing to Liab. Position (Derivatives)
    11500     Position Clearing to Bank Clearing
    11600     Bank Clearing to Position Clearing

  • Use of Correspondence In T&E

    Hi all,
    Watz the use of Correspondence in T&E Management.IF it is for Notification for the attendees regarding the Events that are going to take place then how can we do that using Wizard in IMG settings.....
    I couldn't understand watz Correspondence so plz gimme a reliable answer.

    Correspondence
    Use
    The Correspondence function lets you output notifications for the various activities and
    transactions that arise in Training and Event Management.
    Features
    _ You can output notifications in Training and Event Management either automatically or
    manually.
    You must first carry out the step Assign Notification Abbreviations and Activities [Ext.] in
    Customizing for Training and Event Management.
    Forms that serve as templates for the documents you want to output are assigned to the
    notification abbreviations.
    _ You can set up automatic output of notifications to a predefined output device or medium for
    certain activities in Training and Event Management.
    The output media available include printer, e-mail, fax and telex. If you do not specify an
    output medium, there is no automatic output.
    _ From the recipient list, you can access a print preview of the notification you want to output
    (for manual output).
    _ You can call the manual output function in the dynamic Attendance Menu under Attendance
    _ Correspondence
    When you use the manual output function, you have the additional option of downloading
    documents into MS Word Form Letter.
    _ Each item of correspondence output is recorded in a correspondence history that logs what
    notifications are output to whom.
    See also:
    The documentation for the Customizing activities in Training and Event Management under Dayto-
    Day Activities _ Correspondence.
    Manual Output of Correspondence
    Use
    This function lets you manually trigger output of documents to business event attendees and
    instructors in Training and Event Management.
    This function supplements the automatic output function in that it lets you output documents
    manually as required if errors occurred during automatic output or you require additional
    documents.
    Features
    _ Output to any medium, for example, printer or Internet mail.
    If you select a medium for manual output, you override the standard settings made in
    Customizing for Training and Event Management under Define Attendee Type
    Specific Output Control [Ext.].
    If there is no medium set in Customizing and you do not specify one for manual
    output, documents are output to printer by default.
    _ Output using the Microsoft Word Standard Letter function
    This function is only available with manual output.
    _ Output to screen
    _ Display print preview of notification
    _ Display log of documents output
    _ Display correspondence history for recipients
    Activities
    1. You access this function on the SAP Easy-Access screen under SAP Standard Menu _
    Human Resources _ Training and Events _ Attendance _ Correspondence _ Manual
    Output or in the Attendance Menu under Attendance _ Correspondence _ Manual Output.
    2. You enter an activity and a notification abbreviation (assigned to a specific notification).
    3. You select an output medium as required.
    4. You specify the business event and attendees for which you want to output the notification.
    5. You use the functions available on the recipient list screen (for example, print preview or
    download to MS Word).
    6. You trigger output.
    Outputting Correspondence Manually
    Procedure
    1. On the SAP Easy Access screen, in the SAP Standard Menu choose Human Resources _
    Training and Events _ Business Events _ Attendance _ Correspondence _ Manual
    Output.
    2. Enter the required activity and a notification abbreviation.
    3. Choose data screen.
    4. Enter the business event for which you want to output notifications.
    5. Enter an attendee type where relevant.
    6. Enter an attendee corresponding to the attendee type specified.
    Entries 5 and 6 are optional. If you make no input, all attendees booked are
    proposed as recipients.
    7. Enter the number of N.N. notifications (for group attendees) you want output.
    8. Choose .
    List screen:
    1. Select the attendees in the recipient list for whom you want to output notifications.
    2. If required, change the default output medium (multiple selection possible).
    3. Use the functions available on the recipient list screen, where required:
    Print preview
    MS Word
    MS Word Standard Letter
    Screen output
    Display log
    Display booking data
    Display correspondence history
    4. Choose .
    Result
    The notification is output to the selected output medium.
    Correspondence History
    Use
    The Correspondence History function records the individual items of correspondence output for
    activities in Training and Event Management.
    If you set output to automatic, you can use the history function monitor document output.
    For example, you can use the history function to report on what documents have been sent to
    attendees in a given time period or if and when an attendee received definite confirmation of
    registration, a cancellation notification and so on.
    Features
    You can request reports with the correspondence history functions from four different
    perspectives:
    _ From the perspective of the event type
    If you enter a business event type, all documents that have been output in connection
    with the business event type, such as prebooking notifications, are listed.
    _ From the perspective of the event
    If you enter a business event, all documents that have been output in connection with the
    business event, such as confirmations of registration, are listed.
    _ From the perspective of the output agent
    If you enter an output agent, the report lists all documents that have been output
    manually or automatically by the agent in question. For example, if a booking operation
    triggered automatic output of notification to the recipients, these notifications are listed.
    _ From the perspective of the recipient
    If you enter a recipient, the report lists all documents that have been output to the
    recipient you enter.
    Within the various views, you can select data to narrow down the report's output:
    _ Document recipients
    _ Booking priority: you can request a report on all of the notifications output to waiting list
    attendees, for example.
    _ Selection period: you can specify a time period yourself or select a predefined one.
    _ Output status: you can select from the following statuses:
    _ No output
    _ Errors during output
    _ Output triggered
    _ Output successful
    _ Activity (logical function code).
    You can start the correspondence history function from the Attendance menu. There,
    you can select a business event type, an event date, or an attendee. By doing so,
    you select the data for the report.
    Activities
    1. On the SAP Easy Access screen, in the SAP Standard Menu choose Human Resources _
    Training and Events _ Correspondence _ History. The Correspondence History selection
    screen appears.
    2. You specify the perspective from which you want reporting carried out: event type, event,
    output agent, or recipient.
    3. You enter a document recipient if required.
    4. You can specify the attendee group by selecting a booking priority.
    5. You can specify the reporting period for the correspondence history.
    6. You can select one or multiple output statuses.
    7. You can specify a particular activity by selecting a function code from the list displayed.
    8. Choose Execute.
    The system outputs a correspondence history based on the selection criteria you specified.
    Regards,
    Amit
    Reward all helpful replies.

  • Training and Events Mgt Correspondences (BOKF-FIX)

    Hello,
    Am  getting the following error when i try to print the correspondence for definite place of confirmation.
    Variables Without Values
    PPVAR - TLAND AttenAdd:Country key
    PPVAR - TSTRS Attendee's street
    PPVAR - T_ORT Attendee's city
    PPVAR - T_PLZ Attendee postal code
    PPVAR - VFAXN Organizer's fax no.
    PPVAR - VTELN Organizer phone no.
    How do i ensure that values are contained in these variables.
    Regards,
    Audrey

    hai
    try with the following ..i have collected this from previous thread..
    PLOGI-TIME = '1'
    SEMIN-APART = 0420
    Created Attendance Type, Quota, Deduction rules etc.
    Configured a Business Event Type, Business Event and Booked a person against the same. I firmly booked the event and did the followup.
    PLOGI PLOGI entry for the integration of Training and Event Management Entry variant
    SEMIN-TIMEP entry to specify the minimum percentage attendance for the business event to create an attendance.
    1001 relationships and the A025 relation between the E and the P has a percentage (PROZT) of 0%. Could it be the reason? If yes, how can I change this value to 100%
    created entires in T779X and it worked

  • Correspondence for Fx Deals

    Hi
    While trying following path to create correspondence for outgoing message , getting following Error.
    'An error occured while creating the original attribute for TRM'
    Path : CTF_COMONI-select one entry with status 'Initiated' . Go to status Function . Select 'Create Message and send.
    Can anyone help
    Regards
    Vimal

    I am having the same issue. Can you please share how you resolved the issue.
    Thank you
    Mahi

  • Training and Events Mgt Correspondences HR_ALL_FIX

    Afternoon,
    Have copied the form for definite confirmation (HR_ALL_FIX) of place into ZHR_ALL_FIX so as to suit the client needs. The problem now is that the attendees addresses are not coming out. when i try and print the correspondence i get the following error.
       Variables Without Values                        
       PPVAR      - TLAND      AttenAdd:Country key                                    
       PPVAR      - TSTRS      Attendee's street                                       
       PPVAR      - T_ORT      Attendee's city                                         
       PPVAR      - T_PLZ      Attendee postal code                                    
       PPVAR      - VFAXN      Organizer's fax no.                                     
       PPVAR      - VTELN      Organizer phone no.    
    How do i ensure that values are contained in these variables.
    Regards,
    Audrey

    Hi Reddy,
    Thanks for the reply.  Yes, I have run RHPROFL0.
    Our Timekeeper stuctural authorization uses a custom evaluation path that starts from the employee's position, and on the position, we have a custom relationship 'Z50' - "Time Admin for".  Here's the eval path:
    S  AZ50 (Time Admin for)         O
    O  B003 (Incorporates)             S
    O  B002 (Is line supervisor of) O
    S  A008 (Holder)                       *
    We tried adding a relationship from the business event to the individual orgs, then adding the follow lines to the eval path:
    O  B036 (Organizes)                  D
    D  B020 (Is a generalization of)  E
    No luck yet, but I'm still experimenting.
    Thanks
    Ryan

  • Recordset definition CONCAT in php

    I am having trouble with the CONCAT not being legal syntax in
    the Dreamweaver Advance Recordset definition dialog?
    For instance:
    | Key | Cost1 | Cost2 |
    --------+----------+------------
    | A | 10.50 | 11.35 |
    "SELECT CAST(t1.Cost1 AS CHAR), CAST(t1.Cost2 AS CHAR) FROM
    t1" is valid syntax and works great, with a result of
    | CAST(t1.Cost1 AS CHAR) | CAST(t1,Cost2 AS CHAR) |
    --------------------------------------+---------------------------------------
    | 10.50 | 11.35 |
    However
    "SELECT CONCAT( CAST(t1.Cost1 AS CHAR), CAST(t1.Cost2 AS
    CHAR)) FROM t1"
    is NOT valid syntax according to Dreamweaver.
    Instead Dreamweaver v8.0.2 changes the above query to read
    "SELECT CAST(t1.Cost1 ASCHAR, CAST(t1.Cost2 AS CHAR)) FROM
    t1"
    and then gives an error message.
    1) The initial syntax is valid and works when applied
    directly against the database.
    2) If I change the autogenerated 'Code' directly and modify
    the SQL Statement back to it's original form and then post the page
    the query executes correctly.
    Am I doing something wrong?

    First: I've been working my way through your book 'Foundation
    PHP for Dreamweaver 8'.
    THANK YOU!
    You have a rare gift.
    Second: Any thoughts on how I might convince Adobe that I
    will not hold it against them if they're hot fix isn't quite ready
    for prime time?
    I got the following very disappointing response to my
    request.
    I'm not interested in starting a rant. I just want to get my
    work done.
    Truth be told I'm starting to get a glimmer on how I can
    solve this for myself by creating my own 'sever behavior', but that
    will have to wait till I finish working through your book.
    None the less I do like to feel supported by the vendors I
    purchase my professional tools from.
    More so, as I'm new to Dreamweaver and am in the process
    determining if this will become my tool of choice.
    As a result support receives very close scrutiny.
    Adobe's response follows:
    <<
    Hi Donald,
    Thank you for contacting Adobe Technical Support.
    I understand you are having issues with using the CONCAT SQL
    function through the advanced recordset in Dreamweaver 8.0.2.
    This is still considered as an emerging issue with the
    Dreamweaver 8.0.2 updater and the engineering team is currently
    working for a fix right now. A fix will be released soon so you
    just need to standby our website for fix releases (
    http://www.adobe.com/go/updates).
    For your new issues, please feel free to contact us again
    using our web-based form:
    http://www.adobe.com/support/email/complimentary
    Thank you for understanding, and have a nice day.
    Best regards,
    Christine R.
    Technical Support Engineer
    Adobe Systems
    A web based center providing TechNotes and documentation for
    known product issues:
    http://www.adobe.com/support
    Please use your incident number 8574947 in any correspondence
    with us.
    Technical Support at Macromedia, now part of Adobe Systems
    http://www.macromedia.com/support/
    Note concerning Attachments: Please do not send attachments
    in a reply to this email.
    Instead, can you please contact the support agent to make
    arrangements to send your files.
    Thank you.
    >>

  • Customer correspondence through email

    Hi experts,
    Anyone has any inputs/pointers on how to generate AR correspondence, such as balance confirmation, statement of account, etc through E-mail?
    Any inputs on this regard would be highly appreciated.
    Thanks,
    Shiv

    Start of by reviewing the IMG activities in Finacial global settings.
    Correspondence
    In the following activities, you make the settings for correspondence with your business partners and for internal purposes.
    The correspondence function in the standard system is set up for mailing letters. To fax or e-mail correspondence, see the activity Develop enhancements for correspondence.
    Correspondence includes:
    Payment notifications
    Account statements
    Bill of exchange charges statements
    Internal documents
    Individual letters
    Document extracts
    Balance confirmations
    First you make the fundamental specifications for the aforementioned correspondence types in the following activities.  Specific definitions for each correspondence type are made at other points in the IMG.
    SCOT sends them out. Once you have your email server set up at any list, report etc you create you can select send and then you go to business workplace and it can then be emailed.

  • Create TRM task with resource element assigned

    hi all.
    I want create a TRM tasks with the resource element yet assigned.
    There are some customize action or Add-in to do this???
    Thanks a lot
    Ismael

    Hi,
      Tasks automatically get created based on Transfer orders with the help of this BADI and program:
    LTRM_RQST_GLOBL_SCAN. Look at example  implementation class inside BADI definition.
    After implementing this BADI.
    Call this Function Module to create tasks automatically:
    LTRQ_REQST_SCHDL or you can set up this program RLTRQSCHEDULER in background
      For you to assign a task , use the following FM:
    LTSK_TASK_ASSIGN
    Hope this helps
    Thanks
    Vinod.
    Edited by: Funko Technical on Jan 20, 2010 8:47 PM

  • XML Publisher report definitions not opening

    Id like to reimport all the XML Pub Report definitions into my PS instance.
    I have a PT 8.49 instance and whenever i click on the report definitions of the XML publisher i get this JAVA error:
    "Java Exception: java.lang.NoCl assDefFoundError: com/peopleso ft/pt/xmlpublisher/PTRTFPocess or: finding class com.peopleso ft.pt.xmlpublisher.PTRTFPocess or (2,725) PSXP_ENGINE.RTFProc essor.OnExecute  Name:generate XSL  PCPC:239  Statement:9 Called from:PSXP_RPTDEFNMANAGE"
    SCREENSHOT: http://imageshack.us/photo/my-images/4/al4q.png/
    I was thinking maybe I could export the report definitions from a working instance and import here. Does that seem like a solution that will work

    PSXPCLEAN isnt part of PT 8.49
    So i tried instead to migrate XMLP definitions using Application Designer from a working instance of PS CS.
    But there error is still the same:
    "Java Exception: java.lang.NoClassDefFoundError: com/peoplesoft/pt/xmlpublisher/PTRTFPocess or: finding class com.peoplesoft.pt.xmlpublisher.PTRTFPocess or (2,725) PSXP_ENGINE.RTFProcessor.OnExecute  Name:generate XSL  PCPC:239  Statement:9 Called from:PSXP_RPTDEFNMANAGE"
    Notice the underlined part.
    In the working instance it is "PTRTFProcess" not "PTRTFPocess"

Maybe you are looking for

  • Java.lang.Exception: org.hibernate.AssertionFailure: scrollable result sets

    Hi All, I am using Oracle 11g and I am trying to delete some records from database using some GUI. In that case I am getting following error: java.lang.Exception: org.hibernate.AssertionFailure: scrollable result sets are not enabled. When I restart

  • Oracle V11.2.0.3 ORA-01578: ORACLE data block corrupted - OBJECT = IDL_UB1$

    Hi, I am running into a data corruption issue. My database is: SQL> select banner from v$version; BANNER Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production PL/SQL Release 11.2.0.3.0 - Production CORE 11.2.0.3.0 Production TNS for

  • Code Completion indesign cs3 VS C++ 2005

    Hello everyone, Has anyone been able to make the intellisence working for InDesign cs3 plugin developing with VS C++2005 I was referring to a post long ago for InDesign cs2 VS C++ 2003 http://forums.adobe.com/message/1304438#1304438 But I'm getting t

  • Flash Player 11.8 has no sound

    I am having problems getting sound from video and YouTube due to recent installation of Flash Player 11.8.800.94 on  Mac OS X Lion 10.7.5. I have installed, deleted and re-installed with no luck.

  • Server Side Page Buffering

    I have the following page flow that I would like to mimic: 1: User enters criteria on a page, search or otherwise 2: Page is submitted (server starts rendering a page that takes a long time) 3: The user is redirect to a page w/ an AJAX query that pol