Basic type question

Hi guys. I created a sequence of animated type. I used one of the preset live type styles "manic" . What I want to know is after the type has finished writing the text how do I have the words staying in the sequence and still being animated ie; jittering on the screen.
I have found a interum solution of placing a jpeg of the last frame as the remainder of the clip but the problem with that is it's not animated.
Can anyone help?
Thanks in advance.
Will.

Highlight your track
IN the Inspector, highlight the Timing tab and increase the quantity of Loops with the slider or by typing the new quantity in the box

Similar Messages

  • IDOC question on Message type and Basic Type - Partner Profile

    Hi all,
    I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
    My question is about the setup of Partner Profile creation (WE20).
    When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
    Questions:
    1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables.  I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
    2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
    Thanks.
    tuff

    Tuff,
    Below are my thoughts,
    There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
    OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
    Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order -  ORDRSP.
    And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
    Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
    In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
    2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
    Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
    Regards,
    Chen

  • Unable to extend the basic type "SALESORDER_CREATEFROMDAT202"

    HI
    when iam trying to extend the IDOC basic type "SALESORDER_CREATEFROMDAT202" iam getting an error message "Action is not possiable for generated IDOC types"
    To my understanding SALESORDER_CREATEFROMDAT202 is a bapi.So, I guess we can not extend these type of IDOC directly.
    Can any one can help me how to copy the BAPI interface and extend it....
    or any other solution for this......
    can any one can help me reg this.....

    I will answer my question!
    This is the proble of version we are useing!
    the extenction is possiable in sap 4.6 version.
    but it is not possiable in ecc6.
    So follow the steps i have done
    created a new basic type "ZSALESORDER_CREATEFROMDAT202"
    where icopy the basic type "SALESORDER_CREATEFROMDAT202" to it
    Then i extened the IDOC "ZSALESORDER_CREATEFROMDAT202"
    and added the new segments.
    FInally while assiging the basic type to extended IDOC  given basic type as "SALESORDER_CREATEFROMDAT202"
    And assigned to the message type "SALESORDER_CREATEFROMDAT2"  to it
    then we can use this Structure with
    Message type: SALESORDER_CREATEFROMDAT2
    Basic type: SALESORDER_CREATEFROMDAT202
    Extended:SALESORDER_CREATEFROMDAT202EX
    for data picking u can code in the followin function modules:
    Function Module for Outbound ALE
       ALE_SALESORDER_CREATEFROMDAT2
    Function Module for Inbound ALE
       IDOC_INPUT_SALESORDER_CREATEFR
    There is another method also for this:
    create a bapi fm with all the requirements and go to swo1 tc create an object with method as BAPI FM created.then go to TC bdbg and create a bapi ale interface.this  will automatically generates the inbound and outbound FM's .Then the idoc will be generated with the added segments...

  • IDOC and Basic Type

    Hi Experts,
    I have a basic type that I will use in my IDOC with no process codes(attached FM) that will create a document (e.g. orders, deliveries)... and I have found out a BAPI that I can use in creating the document.. the question is.. do I still need to  CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND' after calling the BAPI to create the document?
    Thanks!
    Nosaj

    Hi,
    Thanks. To clarify.. first I will receive an IDOC coming from XI this IDOC containes the planned orderse that I will create in SAP.
    Question: Can one IDOC contains a lot of planned orders to be created? Meaning that I have created a copy of segment E1PLAFL because this segment can only acquire a maximum of 1 data record... so i copy it and customize it to acquire more than 1 data records.....?
    Then the Basic Type:  LOIPLO01 does not have a functionaly of creating planned orders.. so I will use a BAPI in creating the planned orders....
    Question: Since I will be using a BAPI to create the IDOC.. do I still need to call the function module ive said (WRITEIDOC)?

  • IDOC approach (Basic type : CREMAS01) to upload legacy vendors

    I am using the IDOC approach (Basic type : CREMAS01) to upload legacy vendors.The LSMW then creates default partner functions.
    However i need to modify the partner function.
    My question is ...Is there a way to delete an entry through LSMW using IDOC approach (or even modify would help) but not append????
    Thanks in advance ,
    naval kishore  bhatt.

    Hi,
    Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
    The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
    The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
    The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    Regards,
    Gowri.S

  • IDOC Segement Release vs IDOC Basic Type

    Hi there,
    we are in an upgrade project and are runing into a general question about idoc creation.
    Here is our behavior:
    1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
    2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt  E1MAKTM with fields  MSGFN SPRAS MAKTX.
    3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
    4. In Distribution Model in outbound parameters, added our ZMATMAS.
    As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
    We are using MATMAS03 because this interface exists since 46B.
    Now we send an Material with BD10 and Message Type ZMATMAS.
    The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
    But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
    The additional fields were filled with the NODATA sign.
    My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
    The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
    Why is SAP using the highest available segemnt release regardles which basic type we choose?
    Isnt this wrong?
    Additional infos:
    We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
    Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
    If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
    I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
    Kind regards
    Manuel

    Additional Info:
    In WE21 at the TRFC Port, it is possible to set this Option:
    Send Only Fields of Selected Segment Version
    The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
    But if we are using an reduced message type, all fields of the newest release are in the segement.
    The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
    But it is never called when createing an material IDOC with BD10.
    Bug or feature?
    Kind regards
    Manuel

  • IDOC basic type

    Hi guys,
    Is there anyway to find out the right Basic type which suites our requirement?
    Sahil

    Hi Michal,
    My requirement is whenever a material is created/changed an IDOC should be triggerd.
    we are using change pointers concept here.
    MASTERIDOC_CREATE_SMD_MATMAS is used to record the changes and its get triggerd when we create/change and then pass the idoc to PI for further processing.
    I am also extending my IDOC by adding few fields.
    My question is:
    1.How do i know which basic type to use?
    2.Do i need to populate the fields for an extended IDOC using some enhancements/EXITs or just pass the extended IDOC to PI?
    please reply
    Sahil

  • IDoc basic type FIDCCH01 with error F5866

    Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type.  Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc.  I do not see an idoc value by this name.  What am I missing in my config?
    Thanks,
    Stan

    Stan,
    First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function.  This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received.  These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc. 
    ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank.  This is why I assume that the IDoc in question is missing a value for the AWREF field.
    Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI.  This IDoc type contains a segment E1FIREF with field AWREF.  You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
    Cheers,
    Jamie

  • What is message type, basic type and logical message?

    I have a question with EDI.
    What is message type? what is basic type? what is logical message?
    I am a bit confused. I appreciate your links that you may provide, but even if you can brief me in a few sentences, that will be great.
    Thank you,
    Krishen

    A Message type indicates the type of business document that you are trying to transmit or receive.
    A BASIC type is the IDOC type, which is the actual document that is being exchanged. A message type can be associated with different IDOC types and depending on the requirement you can choose the appropriate one.
    A logical message is nothing but the message type.
    Regards,
    Ravi
    Note : Please mark all the helpful answers

  • Error: Basic type 'WVINVE03' is unknown

    hi sdn frnds
    I am doing File to Idoc scenario in that i am getting the error as
    Error: Basic type 'WVINVE03' is unknown
    can any one know about this and how to solve this problem
    thanks in advance
    Vasu

    Hi,
    where do you try to find this idoc?
    this IDOC should only be in the R3
    (not in the XI)
    if you want it in the XI you need
    to download it's sigmature in <b>integration repository</b>
    just like described here:
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • How to change the default IDOC basic type from CREMAS05 to CREMAS04.

    Hi All,
    How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
    When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
    I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
    Thanks
    Sai Krishna

    execute WE20 and edit the outbound parameters
    here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
    Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

  • Error in idoc of basic type artmas05 - status 51 with Message no. MG537

    Hi all,
         I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
    *The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
    field; it does not contain an entry
    *The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry        
    *The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    *You have not fully maintained the tax classifications
    *The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
    It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
    Thanks in advance,
    Revathi.

    Hi,
    Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
    The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
    The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
    The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    Regards,
    Gowri.S

  • Reg : The functionality of WMMBID02 Basic type in SAP.

    Hi All,
    Can anyone give me the functionality of WMMBID02 Basic type in SAP. Mean, not the structure of the Idocs i am talking about. But to which Module of SAP is it related to and what kind of inventory data it carries? what the significance of this data. which table get updated when this idocs gets posted successfully.
    And also that, From table /GLB/RGTTPLANHED, we can get the trip status. So wat exactly this trip status indicates?... can anyone explain this in detail?

    The message typer for this is WMMBXY and its used for Goods movement between storage location. This would internally calls MB01 transaction and related to MM module.

  • How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

    I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
    The requirement looks very simple but for this, as per my knowledge, I have to create a new  Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
    It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
    Can we do it any other way to handle this kind of situation?
    Thanks in advance for your suggestions and help.

    Hi Phani,
    You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi  to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
    3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
    4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
    Let me know if this helps.

  • Msg basic type idoc_type   unknown ?

    Hi,
    i am workin on file 2 idoc scenario.
    on XI  created rfc destination using sm59
             went to idx1 created port and assigned the rfc destin
        In idx2 i was able to load one idoc but remaining
         shows the message basic type <idoc_type> unknown.
    Can any one help??
    regards
    fariha

    Hi Kazi,
    for File to IDOC no need for IDX2
    Check my link at wiki for File to IDOC
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
    Sachin

Maybe you are looking for