Text id mandatory while saving Billing document

Hi Folks,
            I need to create one new text id and have to make it mandatory at the billing header level i.e. the system should not allow to save the billing document untill an unless some text is given in this newly created text id.
           In the configuration I know we cant make the text id mandatory at the invoice level but that's my requirement as I want in my order and delivery the text to be blank.
I dont want to flow them from the preceding document.
          So can some suggest any user-exit or scren exit or any other alternative through which I can achive the above requirement,the previous message posted with this requirement are of no use to me.
Thanks in advance!!!
Regards,
Ashish

Hi Suresh,
              Thanks for your responce...I'll update you about the exact requirement and our findings...
I have 6 Sales order types so whenever a billing doc. is created for this for 3 of them a default value should appear in this newly created text id which we think is posible through coding the same in USER_EXIT_SAVE and making the new text type mandotory in the config.for Sales Order Header.
              Whereas for the other 3 order type I want the text to be blank at Order level so I cant make it mandatory for these Order types but it should not allow to save the billing doc.for these order types without entering the text,I need answer for this requirement and also the default value at Invoice level should be editable.
Hope you understand the exact requirement.
Just need an answer to the below question in YES or No.
Can we make text mand. at invoice level or not???
Regards,
Ashish
Edited by: Ashish Gaurav on Jun 14, 2009 4:53 PM

Similar Messages

  • Can i know the user exits which should trigger while saving billing docu

    hi,
    please can u help me to find out user exits which should trigger while saving billing documents.

    A couple years ago I downloaded this program, I think from SAPFANS.  I don't take any credit for it...Not sure who originally wrote it.  Just type in the t-code and hit execute. 
    *& Report name          : Identify and Drill-Down to SAP User Exits.   *
    *& Program name         : ZZ_FIND_USER_EXITS                           *
    REPORT  ZZ_FIND_USER_EXITS
      NO STANDARD PAGE HEADING
      LINE-SIZE 132
      LINE-COUNT 65
      MESSAGE-ID MM.
    D A T A   D E F I N I T I O N                                        *
    TABLES : TSTC,      " SAP Transaction Codes
             TADIR,     " Directory of Repository Objects
             MODSAPT,   " SAP Enhancements - Short Texts
             MODACT,    " Modifications
             TRDIR,     " System Table TRDIR
             TFDIR,     " Function Module
             ENLFDIR,   " Additional Attributes for Function Modules
             TSTCT.     " Transaction Code Texts
    S E L E C T I O N   S C R E E N                                      *
    PARAMETERS : P_TCODE LIKE TSTC-TCODE OBLIGATORY.
    I N T E R N A L   S T R U C T U R E S   &   T A B L E S              *
    DATA : GT_TADIR LIKE TADIR OCCURS 0 WITH HEADER LINE.
    V A R I A B L E S                                                    *
    DATA :
           GV_FIELD1(30)  TYPE C,
           GV_DEVCLASS    LIKE TADIR-DEVCLASS.
    C O N S T A N T S                                                    *
    CONSTANTS:
               GC_F     LIKE TRDIR-SUBC   VALUE 'F',
               GC_R3TR  LIKE TADIR-PGMID  VALUE 'R3TR',
               GC_FUGR  LIKE TADIR-OBJECT VALUE 'FUGR',
               GC_SMOD  LIKE TADIR-OBJECT VALUE 'SMOD',
               GC_PROG  LIKE TADIR-OBJECT VALUE 'PROG'.
    R A N G E S                                                          *
    RANGES:
      GR_VKORK      FOR  WKBP-VKORG.
    E V E N T   P R O C E S S I N G                                      *
    INITIALIZATION.
    AT SELECTION-SCREEN.
      SELECT SINGLE PGMNA
        INTO TSTC-PGMNA
        FROM TSTC
        WHERE TCODE = P_TCODE.
      IF SY-SUBRC <> 0.
        MESSAGE E899(MM)
          WITH TEXT-E01    " Input Transaction Code is Invalid.
               TEXT-E02.   " Please Correct !!
      ENDIF.
      SELECT SINGLE TTEXT
        INTO TSTCT-TTEXT
        FROM TSTCT
        WHERE SPRSL = SY-LANGU
          AND TCODE = P_TCODE.
    START-OF-SELECTION.
      CLEAR GV_DEVCLASS.
      SELECT SINGLE DEVCLASS
        INTO GV_DEVCLASS
        FROM TADIR
        WHERE PGMID  = GC_R3TR
          AND OBJECT = GC_PROG
          AND OBJ_NAME = TSTC-PGMNA.
      IF SY-SUBRC <> 0.
        SELECT SINGLE SUBC
          INTO TRDIR-SUBC
          FROM TRDIR
          WHERE NAME = TSTC-PGMNA.
        IF TRDIR-SUBC = GC_F.         " Function Group
          SELECT SINGLE FUNCNAME
            INTO TFDIR-FUNCNAME
            FROM TFDIR
            WHERE PNAME = TSTC-PGMNA.
          SELECT SINGLE AREA
            INTO ENLFDIR-AREA
            FROM ENLFDIR
            WHERE FUNCNAME = TFDIR-FUNCNAME.
          CLEAR GV_DEVCLASS.
          SELECT SINGLE DEVCLASS
            INTO GV_DEVCLASS
            FROM TADIR
            WHERE PGMID    = GC_R3TR
              AND OBJECT   = GC_FUGR
              AND OBJ_NAME = ENLFDIR-AREA.
        ENDIF.
      ENDIF.
      SELECT *
        FROM TADIR
        INTO TABLE GT_TADIR
        WHERE PGMID  = GC_R3TR
          AND OBJECT = GC_SMOD
          AND DEVCLASS = GV_DEVCLASS.
      FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
      WRITE:/(19) 'Transaction Code - ',
              20(20) P_TCODE,
              45(36) TSTCT-TTEXT.
      SKIP.
      IF NOT GT_TADIR[] IS INITIAL.
        WRITE:/(95) SY-ULINE.
        FORMAT COLOR COL_HEADING INTENSIFIED ON.
        WRITE:/1 SY-VLINE,
               2 'Exit Name',
              21 SY-VLINE ,
              24 'Description',
              95 SY-VLINE.
        WRITE:/(95) SY-ULINE.
        SORT GT_TADIR BY OBJ_NAME.
        LOOP AT GT_TADIR.
          SELECT SINGLE MODTEXT
            INTO MODSAPT-MODTEXT
            FROM MODSAPT
            WHERE SPRSL = SY-LANGU
              AND NAME = GT_TADIR-OBJ_NAME.
          FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
          WRITE:/01 SY-VLINE,
                 02 GT_TADIR-OBJ_NAME HOTSPOT ON,
                 21 SY-VLINE,
                 22 MODSAPT-MODTEXT,
                 95 SY-VLINE.
        ENDLOOP.
        WRITE:/(95) SY-ULINE.
        DESCRIBE TABLE GT_TADIR.
        SKIP.
        FORMAT COLOR COL_TOTAL INTENSIFIED ON.
        WRITE:/ 'No of Exits:' , SY-TFILL.
      ELSE.
        FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
        WRITE:/(95) 'No User Exit exists'.
      ENDIF.
    AT LINE-SELECTION.
      GET CURSOR FIELD GV_FIELD1.
      IF GV_FIELD1(8) = 'GT_TADIR'.
        SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
        CALL TRANSACTION 'SMOD' AND SKIP FIRST   SCREEN.
      ELSE.
        MESSAGE I899(MM)
          WITH TEXT-I01    " Click on the Exit Name to Drill-Down
               TEXT-I02.   " to SAP Enhancement Information.
      ENDIF.
    END-OF-SELECTION.
    TOP-OF-PAGE.
    S U B R O U T I N E S                                                *
    E N D   O F   R E P O R T  ****************************************

  • Find out user exits which should trigger while saving billing doc.(VA01)

    Hi All,
    please can u help me to find out user exits which should trigger while saving billing documents for VA01 transaction...I have already z report to find the user-exit for any transaction.I have tried in that also.
    Reply
    Ulhas

    Hi
    Try these
    USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)                    
    The internal number range used in the standard system is specified                
    in the billing type table and can be changed in this user exit. This              
    user exit is only called when the billing documents is created.                                                                               
    USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program                       
    RV60AFZZ)                                                                         
    In this user exit additional fields for account determination that                
    are not provided in the standard system are copied into                           
    communication structure KOMKCV (header fields).                                                                               
    USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)                               
    In this user exit additional fields for account determination that                
    are not provided in the standard system are copied into                           
    communication structure KOMPCV (item fields).                                                                               
    USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program                     
    RV60AFZC)                                                                         
    Depending on the number range, table TVFKD is used to set the                     
    billing date (country-specific requirments in Italy).                             
    USEREXIT_NUMBER_RANGE is automatically deactivated when this user                 
    exit is being applied.                                                                               
    USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)                  
    This user exit is only called when the billing document is created.               
    It is used to provide the header and the item of the new billing                  
    document with deviating or additional data.                                       
      USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)                    
      Printing the item line of a billing document can be supplemented or             
      changed.                                                                               
    USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)                     
      Printing the header line of a billing document can be supplemented              
      or changed.                                                                               
    User exits in program RV60AFZD                                                  
      Short descriptions of the user exits are contained in the program:                                                                               
    -   USEREXIT_RELI_XVBPAK_AVBPAK                                                                               
    -   USEREXIT_NEWROLE_XVBPAK_AVBPAK                                                                               
    -   USEREXIT_NEWROLE_XVBPAP_AVBPAK                                                                               
    e following user exits are available in report SAPLV60B for transfer              
    accounting (function group V60B):                                                                               
    EXIT_SAPLV60B_001: Change the header data in the structure acchd                
      You can use this exit to influence the header information of the                
      accounting document. For example, you can change the business                   
      transaction, "created on" date and time, the name of the person who             
      created it or the transaction with which the document was created.                                                                               
    EXIT_SAPLV60B_002: Change the customer line ACCIT                               
      You can use this exit to change the customer line in the accounting             
      document. This exit is processed once the ACCIT structure is filled             
      in with data from document header VBRK.                                                                               
    EXIT_SAPLV60B_003: Change the customer line in costing                          
      The customer line is filled in differently for costing. You can use             
      exit 003 to influence the ACCIT structure.                                                                               
    EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add          
    information to a GL account item (such as quantity specifications)     
    with this exit.                                                                               
    EXIT_SAPLV60B_005: User exit for accruals                              
    Once all relevant data for accruals was entered in the GL account      
    item, you can add to this data with this exit.                                                                               
    EXIT_SAPLV60B_006: Change the control line ACCIT                       
    You can use exit 006 to add information to the control line.                                                                               
    EXIT_SAPLV60B_007: Change the installment plan                         
    You can use exit 007 to add information to the installment plan        
    parameters in the GL account item.                                                                               
    EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and      
    ACCHD                                                                  
    After the accounting document is filled in with data, you can use      
    exit 008 to change the document once again.                                                                               
    EXIT_SAPLV60B_010: Item table for customer lines                       
    You can use exit 10 to influence the contents of customer lines        
    before they are created.                                                                               
    EXIT_SAPLV60B_0011: Change the parameter for cash account              
    determination or reconciliation account determination                  
    You can use this exit to change inbound parameters in order to         
    influence account determination.                                       
    >                                                                      
    Thanks
    Shiva

  • 'update was terminated' while creating billing document VF01

    Hi all,
             i need a solution urgently ..except for paticular document no all documents that i post using VF01 create successfully document no.
    but for a paticular document no(may be it is of some type that i am unable to) while creaing billing document no it gives a message 'document created successfully' ,but when i try to click any button after that e.g BACK it shows a messge 'Update was terminated  for author ....' in my inbox. and vf03 shows the documentdoesn't exist.
    in st22 i checked one dump . when i gave a break point at that point the cursor never reached the code.
    I also checked SM13 and it showed all fms as init. and one fm 'RV_MESSAGE_UPDATE ' as error . i aws unable find the fm in the main program .
    one more thing when i create bill document for other document type it shows messge 'Document saved ....(no accounting document created)' but for this one i am getting messge 'document saved.......' .
    I asked one collegue he told me might be some OSS notes required for it . i am working on a unicoded system ECC 6.0  version.but he is not sure .
    Has any body faced the same problem..and what was the soln....if oss notes are required than how could i find it..and what was the no...........
    THANKS IN ADVANCE ...................

    THANKS  for the reply.
    i am new to sap .can u tell me in detail where actually i can check for number range of the document . one more when i checked the sm13 and  started debugging it gave me for a certain character set  (may be in chineses) present in the table ,the transfer command gives a dump. now the problem is it is too long 132 and don't no forwhich character it gives an  dump.how can i check the characters maintained in the system. it gives a dump   CX_SY_CONVERSION_CODEPAGE   ,At the conversion of a text from codepage '4102' to codepage '4110':      
    i am not sure this causes the mesages 'Updation was terminated' . what u people think.
    thanks ..

  • Short dump in queue while transfering billing document to the ECC.

    Hi,
    While transferring billing document to ECC we got the error SYSFAIL and The running application consciously caused an abort.
    please find the attached ST22 dump and do the needful. Please give th mail id i will send dump.
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLCOINT_TP" - in                                  
         "COINT_TPOST_IT_INSERT".                                                                     
        The main program was "SAPMSSY1 ".                                                                               
    In the source code you have the termination point in line 92                                  
        of the (Include) program "LCOINT_TPU03".  
    62     EXPORTING                                                                               
    63       T006_MSEHI = I_MEINH                                                                  
       64     EXCEPTIONS                                                                               
    65       NOT_FOUND  = 1.                                                                       
       66   IF SY-SUBRC = 0.                                                                          
       67     LS_COINT_TPOST_IT-MEHT  = I_MEINH.                                                      
       68   ENDIF.                                                                               
    69   LS_COINT_TPOST_IT-BETRG    = I_BETRAG.                                                    
       70   LS_COINT_TPOST_IT-CURRENCY = I_CURRENCY.                                                  
       71 * Additional data                                                                               
    72   LS_COINT_TPOST_IT-MANDT = SY-MANDT.                                                       
       73   IF NOT I_DATE IS INITIAL.                                                                 
       74     LS_COINT_TPOST_IT-BDATE  = I_DATE.                                                      
       75   ENDIF.                                                                               
    76   LS_COINT_TPOST_IT-REVERSE  = I_REVERSE.                                                   
       77   LS_COINT_TPOST_IT-VORGNG   = COINT_BILLING.                                               
       78 * Derive BUZEI                                                                               
    79   SELECT MAX( BUZEI ) FROM COINT_TPOST_IT INTO LD_BUZEI                                     
       80                                           WHERE GUID = I_GUID.                              
       81 * begin insert note 1003536                                                                 
       82   SELECT SINGLE * FROM COINT_TPOST_IT INTO LS_COINT_TPOST_IT_OLD                            
       83                   WHERE GUID  =  I_GUID                                                     
       84                   AND   BUZEI =  LD_BUZEI.                                                  
       85                                                                               
    86   CLEAR LS_COINT_TPOST_IT_OLD-BUZEI.                                                        
       87   CLEAR LS_COINT_TPOST_IT_OLD-TIMESTMP.                                                     
       88   CLEAR LS_COINT_TPOST_IT_OLD-PROCESSED.                                                    
       89   CLEAR LS_COINT_TPOST_IT_OLD-CHANGED.                                                      
       90                                                                               
    91   IF LS_COINT_TPOST_IT = LS_COINT_TPOST_IT_OLD.                                             
    >>>>>     MESSAGE TEXT-X01 TYPE 'X'.                                                              
       93   ENDIF.                                                                               
    94 * end insert note 1003536                                                                   
       95                                                                               
    96   ADD 1 TO LD_BUZEI.                                                                        
       97   LS_COINT_TPOST_IT-BUZEI = LD_BUZEI.                                                       
       98 * Get TIMESTMP                                                                               
    99   PERFORM GET_TIME_STAMP CHANGING LD_TIMESTAMP.                                             
      100   LS_COINT_TPOST_IT-TIMESTMP = LD_TIMESTAMP.                                                
      101 * Update COINT_TPOST_HD                                                                     
      102   IF NOT LD_INSERT_HD IS INITIAL.                                                           
      103     CALL FUNCTION 'COINT_TPOST_HD_INSERT'                                                   
      104       EXPORTING                                                                               
    105         I_GUID  = I_GUID                                                                    
      106         I_OBJNR = LD_OBJNR                                                                  
      107         I_KOKRS = LD_KOKRS                                                                  
      108         I_DATE  = LS_COINT_TPOST_HD-BDATE                                                   
      109       EXCEPTIONS                                                                               
    110         OTHERS  = 3.                                                                        
      111   ENDIF.                          
    Best Regards,
    Prakesh

    Hi,
    Can you plz help in my issue .
    Dear Gurus,
    Find the below scenario followed by us.
    1.Created the service order with the ZSR3 procurement item category.
    2.PR created for the service order 35035201 in ECC with no 0070088937.
    3.One queue is struck with the below details.
    4.If we re process the queue it will process with out any error and then only our document flow of the CRM service order line item.
    Plz check the queue name R3AD_CRM_SRV_0035025201 in CRM system from
    Tcode SMQ2 which is in SYSFAIL status. The corresponding BDOC in SMW01
    tcode has validation error message " Module CRM_SRV_EXT_VAL, BDoc type
    CRM_SRV_XTN. Message no. SMW3018 " . Plz advise.
    As per my understanding and debugging i think it might be a issue
    As a standard CRM any change/update in ECC document 0070088937 should
    send back the information to the source CRM document with header GUID
    4E6527B4D3070C10E10080000A8C6828 . But system is referring to a
    different GUID where there is no document exist in CRM.
    Pls find the root cause to trigger different GUID when information is
    passed from ECC to CRM system.
    Best Regards,
    Prakesh

  • Error while saving shipment document

    Dear Gurus,
    While saving Shipment document i am getting this error
    Transportation planning point not allowed for export shipment.
    Please note i am not doing export shipment.
    Thanks
    KS

    I have checked all the settings and have found OK.
    I am getting the above error even while making empty shipments, without deliveries.
    I have used the same shipment type & transportation planning point earlier. I did not get these error at that time. I was able to create shipment cost document and other documents.
    Please advise.
    Thanks
    KS

  • Error while changing Billing document

    while opening billing document in VF02 i got got error " Period 001/2011 id not open for account type S  and G/L 1600261"
    can u tell what is that error and how to solve?

    Hi ,
    Check the below thread for reference
    Period 001/2011 is not open for account type S and G/L 421860
    Regards,
    Ajay

  • Error while creating billing documents

    Hi,
      While creating billing documents I am getting error message as 
    Maintain customizing for excise and series group determination
    Message no. 8I619
    I have check the setting for CIN it is OK excise and series group are maintain properly so what can be the proble,
    regards,
    zafar

    Hi,
    Check once again customizing
    Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    - Define excise series groups based on type of outgoing document
    - Assign series group to excise registration ID
    - If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    - If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    - No account postings for CENVAT in sales cycle
    - No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Thanks
    Chidambaram

  • Error while posting billing documents

    Hi,
    I am trying to post billing documents for accounting , but I am getting some error related to number range.
    I have checked number range assignments, where else I can check to find out error.
    Regards
    Nidhi

    If you are getting error while creating billing document -
    Check your number range status assignment in T-Code - VN01
    If any userexit is used then check in Userexit MV60AFZZ. There could be a Z-table where the number range may not be properly defined for the Billing Type/ plsnt/etc. as per the settings.
    If Billing document is created and you get this error while posting-
    Then it would be error with the number range for Accounting Document. Pls. ask the FI person to fix this.
    If the above does not solve - pls. mention the exact error with error code.
    Thanks

  • Error while releasing billing documents to accounting

    i am facing the following problem while releasing billing documents to accounting i.e, taxcode in procedure TAXD is invalid...   pls solve it...

    Hi,
    That means the tax code which you are using is not linked to your tax procedure.
    For this Goto T.Code :FTXP
    Give Country for which this tax procedure is used.
    Next you have to give the Tax Code which you are using, if it is not created in that then it will create that tax code for that country, in that screen you will see all the tax condition types, give your tax percentage to the condition type which you want to use (Say MWST)
    Now release the billing document for accounting.
    You want face the issue.
    Hope this is clear.
    Reward if helpful.
    Thanks
    Praveen

  • Create Excise invoice(J1IIN) document while creating billing document using bapi BAPI_BILLINGDOC_CREATEMULTIPLE

    Dear Experts,
    My scenario is:
    We have batch split scenario, where the parent line item of billing document has 0 quantity and its subsequent item (item with batch number) holds actual quantity data.
    When we create billing document using VF01 against delivery document, system creates billing document along with excise invoice document (J1IIN Document). And in excise document contain same number of line items that of billing document. Please see the below attachment: 
    Biiling document screen shot:
    While creating billing document, the J1IIN Document created automatically. Below is the screen-shot for the same.
    Now the issue is:
    When we create billing document using BAPI: BAPI_BILLINGDOC_CREATEMULTIPLE system creating only billing document and not creating excise invoice document.
    When we create excise document manually using J1IIN the zero quantity line items are excluded in excise invoice document.
    Please see the below screen-shot for the same; The z quantity line items are missing.
    We want excise document to be created while creating billing document using BAPI BAPI_BILLINGDOC_CREATEMULTIPLE. Or is there any other BAPI for the same purpose.
    Customization is also maintained for creating excise invoice document automatically.
    Regards,
    Rajesh Sadula.

    HI
      Pricing will be carried basing on the pricing
    procedure.
    Case1: Prices will be carried out automatically if
    necessary condition records are maintained for the
    condition type.
      For this you can go to Sales Order-> Item Conditions
    In the screen you can click on command button Analysis,
    which gives you the list of condition types associated
    to the pricing procedure. By clicking on the condition
    type you can know the action that has taken place.
    Case2: Manually forcing prices for Items.
      To do this, you have to populate ORDER_CONDITIONS_IN &
    ORDER_CONDITIONS_INX. Also note to identify the item
    numbers, you manually pass the item number for each item
    in the sales order, use the same item number for
    populating conditions.
      Parameters required:
    ORDER_CONDITIONS_IN:
      ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
    ORDER_CONDITIONS_INX:
      ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
       Hope the above info helps you. Do revert back if you
    need more info.
    Kind Regards
    Eswar

  • Unable to see existing documents in a Custom Sharepoint 2013 Document library while saving a document directly in it using explorer mode

    Hi,
    We have a SharePoint 2013 doc library based on a custom template, which has been migrated from 2010.
    We are unable to see existing documents in a Document library created using this template while saving a document directly in it using explorer mode, However we can save files and even see them in explorer mode, only when we try to save a new document there
    directly, we cant see the old docs.
    All the OOB libraries work fine.
    Below is the normal behavior while saving a file, however nothing comes up when saving on this custom template library

    Solved it myself guys... (Well the major part)
    Got help from here...
    https://www.nothingbutsharepoint.com/sites/devwiki/articles/pages/blank-open-save-dialog-when-browsing-document-library-from-office-clients.aspx
    and
    http://www.sharepointconfig.com/2011/02/vs2010-list-definition-template-missing-file-dialog-view/
    with some tweaks of my own..
    Still working on it because its showing SharePoint 2010 header... And I need 2013 look...

  • Copy text from outbound delivery to billing document

    Hi Gurus,
    Is there a way to copy a text from outbound delivery to billing document?
    I found text determination. It is only possible to maintain text from Sales to Billing.
    Thanks.
    Stéphane.

    Hi,
    Goto the T.Code "VOFA".
    Select your billing type.Details.
    Goto "Output/partners/texts" tab.
    Maintain the "Textdeterm. procedure" as the procedure same as your delivery.
    Anotehr way is goto the T.Code "VOTXN".
    Here click on "Delivery Header".
    Check the check box for "Reference".
    Regards,
    Krishna.

  • Copying Text From Sales order to Billing Document

    Hi all,
    I have searched all posts for my issue but found nothing so that i am posting this issue.
    I want to copy the Some text form sales order to billing document is there any cnfig to do this
    order is there any exit for billing in which i can write code to copy text from sales order to billing document.
    please provide me a solution.
    Thanks in adavnce.
    Vinod.

    Hi,
    Use the same t-code VOTXN to do access sequence assignment.
    When you choose text object Billing Doc (header/item), there is 3 folders in dialog structure:
    - Text procedure
    - Access sequence
    - text procedure assignment
    In the text procedure folder, select related text procedure, then assign the created access sequence to respective text id.
    Hope this help.
    Cheers,

  • Changing billing document date while creating billing document from vf01

    Hi gurus,
    I have requirement to change billing doc date while creating billing document from VF01.
    here I have to consider goods issue date eq billing date.
    caluculating billing date = Goods Issue + Goods in Transit duration time.
    I have done everu thing but I cant update the caluculated date, iam using the following enhancement
    Enhancement:SDVFX001
    Function Module:EXIT_SAPLV60B_001
    Include:ZXVVFU01 which are part vf01.
    here iam sending the calculated date to VBRK-FKDAT
    move cal_date to vbrk-fkdat.
    need help how to update the calculated date to VBRK-fkdat i.e billing document date
    Regards
    Bhaskar

    Hi
    No! That exit is not good for your issue
    U can use the user-exit USEREXIT_NUMBER_RANGE_INV_DATE  defined in RV60AFZC
    Max

Maybe you are looking for