SC not  in the sourcing cockpit after the follow-on document is deleted

HI,
    In  sourcing cockpit ,  I created a contract by SC , but  I  deleted the contract , the SC didn't appear in sourcing cockpit.  the SOURCE_REL_IND  still is 'Y',    I have no way to create new contract by the SC .
   I don't know if it is the standard functionatity,  It seem to be not reasonable.
  Please tell me the solution  that SC can be back to sourcing cockpit  automatiocally.
  even if I  carry out the BBP_GET_STATUS_2.  it  still don't  work.
   Thanks a lot.
  Jesse

Hi
the rule is below
sc created 2 qty  -- PO created 2 qty -PO deleted - now order quantity and PO quantity difference is there so now SC comes to cockpit and this shopping cart item  needs to sourced and PO needs be created.
i did not test below scenario.
SC CREATED - contract or Bid invitation  created and now Contract / bid invitation deleted and now you are expecting this sc item comes to cockpit.
Note 1068497 - BBPSC04: Incorrect status for items completed in sourcing
Symptom
You create a shopping cart which is sent to sourcing cockpit. You create a follow-on document. For eg: Bid invitation. You delete the same and complete the item in sourcing. The status of the item in check status is shown as 'Approved' instead of 'Cannot be ordered'.
As per the above note sap rule, even though Bid Invitation deleted and reference shopping cart must venture to cockpit to create another follow on document.in your case SOURCE_REL_IND = Y instead of X. What is the item status of  sc after contract / po deleted?

Similar Messages

  • The Shopping cart not appearing in the sourcing cockpit of the buyer

    Hi
    We are using Extended Classic Scenario. The SC was created in SRM and then after approval was send to a central buyer for sourcing. The central buyer redistributes the same to the respective Buyer based on the purchasing group. However the SC doesnt appear in the sourcing cockpit of the actual buyer and when I see the details of the SC item in BBP_PD, I see that the Sourcing Relevant Indicator is marked 'Y' which means Sourcing is already completed. But nowhere a supplier has been added to the SC by anyone and it also doesnt reflect in the BBP_PD.
    Any idea how and why the indicator has the status 'Y' and how can I make the SC appear in the sourcing cockpit of the buyer.

    Hi Manoj,
    If the SC is directly converted into a P.O (either ordered / held status) please check the Sourcing settings in SPRO.
    SPRO > IMG > SRM > SRM Server > Sourcing > Define sourcing for product categories
    Check whether sourcing always carried out was maintained for the required product category. The P.O will get directly created in case the setting is " Sourcing never carried out".
    Please check this and let me know if this is the case.
    Rgds,
    Teja

  • Warning: Failed to clean up the source mailbox after the move

    Hi!
    After moving a mailbox between databases (EMC or EMS), there is a warning: Warning: Failed to clean up the source mailbox after the move. Erro details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634).
    Users can successfully access mailboxes, but these mailboxes stay in disconected mailbox node on EMC, and it is shown on EMS afer command [PS] C:\> Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} and their databases are
    the old ones.
    We have recently upgraded from SP2 to SP2 RU4, but we´re not sure when this problem started.
    Our Environment:
    Windows Server 2008 R2 Enterprise SP1
    Windows Roles: File Services, Web Server (IIS)
    Exchange Server 14.02.0318.001 (Build 247.5) Roles MBX, DAG with one more MBX identical Server
    Antivirus: Forefront Endpoint Protection Version: 2.1.1116.0
    Virtualization: Yes – Hyper-V
    Applications: Backup Agent CA, SCCM Agent, SCOM Agent, HP Management Tools
    Any idea?
    Thankyou in advance!
    Fabio Martins MCDST/MCSA Brasil!!!

    I recently upgraded our Exchange 2010 servers (CAS/HUB and MBX) from SP1 to SP3 RU6 and now I'm encountering this issue when doing mailbox moves. I opened a support case with Microsoft and it appears that they are aware that SP 3 RU1 doesn't fix
    the issue in all cases. Below is the response I received from the support engineer.
    =====
    Based on my research and case experience, we have several customers report that even if they are running Exchange 2010 SP3 RU1 or later version(for example, one of customer is running Exchange 2010 SP3 RU4 and another is also in CU6 environment), they also
    have such issue. When they move mailbox, it completed with warning message that source mailbox can’t be cleaned up after the mailbox move operation. This issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox.
    Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move
    process when you move many mailboxes at the same time.
    Currently, the workaround is to remove the “SoftDeleted” mailboxes manually after move the mailbox using the command you shared to us.
    ==========================================
    1.    List all disconnected mailboxes in a database and display DisconnectReason if its SoftDeleted or Disabled
    Get-MailboxStatistics -Database "DB9" | Where-Object {$_.DisconnectDate -Notlike $NULL} | Format-Table DisplayName, DisconnectDate, MailboxGuid, DisconnectReason –Wrap
    2.    Remove a specific softdeleted mailbox
    Remove-StoreMailbox -database “DB9” -identity “User Alias here” -MailboxState SoftDeleted
    ==========================================
    And as I know, it has no impact on the mailbox usage, so we can ignore the warning message currently. Please rest assured that once we got more information about the issue, we will inform you ASAP.

  • Should the vendor in the Shopping Cart be updated from the Sourcing Cockpit

    Hi All,
    hopefully an easy question for someone to answer.
    When a vendor is assigned in the Sourcing Cockpit and the Purchase Order is created should the vendor be updated in the linked shopping cart?
    Cheers
    Chris

    Hi Chris,
    All questions are welcome irrespective of the criticality so you are free to ask anything related to SRM.
    The vendor will not get updated in the shopping cart if you assign a vendor at the time of sourcing while creating a P.O. The same can be checked out by selecting the Source of supply / service agents link in the check status for a particular shopping cart.
    The source of supply field will only be populated when you assign the vendor at the shopping cart level and not during the P.O creation.
    Hope this will make you clear.
    Rgds,
    Teja

  • SOURCE_REL_IND : shopping cart not appearing in the sourcing cockpit

    Gurus,
    Few of the shopping carts after deleting the follow-on PO doesn't appear back in the sourcing cockpit. Furthermore, I found the SOURCE_REL_IND set to blank in table BBP_PDIGP.
    Since this is happening at random, not sure if I can forcefully push the cart into the sourcing cockpit using any FM.
    Thank you.
    PS  : I tried FM : BBP_PDIGP_DB_DIRECT_UPDATE, but the next run of BBP_GET_STATUS_2 is revoking it back to space.

    Hello Ricardo
    SUB:- CLASSIC SOURCING ...
    assume that my buyer is incharge of the sc
    1.requestor creates a sc and buyer also create a PO from the cockpit.
    2. later business decides some thing  wrong so buyer deletes the same PO
    3. after status job the same sc why comes to cockpit. the same buyer should look each time the follow on docuemnts created or not?
    4. what is the SAP stratergy here deleted PO taking to cockpit again
    5. understand many customer has different taste.
    6. if i were buyer which i really deleted the same PO , i dont want to see the the same sc again into cockpit.
    sap has any flexible options ?
    7. any customers reported to sap this is a problem or incidence.
    i do have some incidents in sdn , 2 of them dont like this functionality
    BBP_GET_STATUS _2 - Deleted PO's
    deleted po not taken to the cockpit.
    what is the sap sourcing stratergy describes this scenario ?
    br
    muthu

  • Completed shopping carts again reapearing in the sourcing cockpit

    Hi,
    We are facing a problem for the sopurcing cockpit. There are some shopping carts which are created from the catalogs and after approval purchase orders are getting created without any problems.
    Next day these shopping carts are coming into the sourcing cockpit. This is happeneing only for a perticular company code whose corresponding backend R/3 resides on a differetent box.
    My question is if the report BBP_GET_STATUS_2 is run and during that time if the backend R/3 is not available what will be the result. Can this cause the shopping carts to reappear into the sourcing cockpit.
    We are on SRM 5.
    Thanks and Regards
    Manoj Upadhyay

    Hi,
    maybe the two notes
    SRM: 1134786       
    Backend: 1123548
    help. They include most of the relevant notes with corrections for BBP_GET_STATUS_2.
    Best regards,
    Georg

  • Custom SharePoint 2010 designer page throws "The data source control failed to execute the insert command" exception while adding the new item after the August 13, 2013 CU has installed

    We have the SharePoint Server 2010 with SP1 environment on which the custom SP2010 designer pages were working as expected before the
    August 13, 2013 CU has installed. But, getting the below exception while trying to add the new item after the CU has installed.
    Error while executing web part: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.SharePoint.WebControls.SPDataSourceView.ExecuteInsert(IDictionary values)     at
    System.Web.UI.DataSourceView.Insert(IDictionary values, DataSourceViewOperationCallback callback) 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
    06/19/2014 16:49:37.65  w3wp.exe (0x1240)                        0x1300 SharePoint Foundation        
     Runtime                        tkau Unexpected Microsoft.SharePoint.WebPartPages.DataFormWebPartException: The data source control
    failed to execute the insert command. 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc    at Microsoft.SharePoint.WebPartPages.DataFormWebPart.InsertCallback(Int32 affectedRecords, Exception ex)     at System.Web.UI.DataSourceView.Insert(IDictionary
    values, DataSourceViewOperationCallback callback)     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.FlatCommit()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.HandleOnSave(Object sender, EventArgs e)    
    at Microsoft.SharePoint.WebPartPages.DataFormWebPart.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.ProcessRequestMain(Boolean
    inclu... 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
    06/19/2014 16:49:37.65* w3wp.exe (0x1240)                        0x1300 SharePoint Foundation        
     Runtime                        tkau Unexpected ...deStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
    I have tried changing the "DataSourceMode" as below, now the insert command is working, but update command is not working.
    <SharePoint:SPDataSource runat="server" DataSourceMode="ListItem" />
    Also, the lookup dropdown fields are displaying the value as "<a href="Daughterhttp://cpsp10/sites/Employees/_layouts/listform.aspx?PageType=4&ListId={8F62F444-FB6A-4F03-9522-C4696B45DCD1}&ID=10&RootFolder=*">Daughter</a>"
    instead of only "Daughter".
    Please provide the solution to get rid of this issue.
    Thanks
    Ramasubbu

    Try below:
    http://social.technet.microsoft.com/Forums/en-US/ae910269-3a0c-4506-844b-e8bc89d95b71/data-source-control-failed-to-execute-the-insert-command
    http://blog.jussipalo.com/2012/01/sharepoint-2010-data-source-control.html
    While there can be many causes for this generic error message, in my case the first parameter or ddwrt:DataBind function inside the SharePoint:FormFields element was
    'i' and I was working with an Edit Form. Changing it to
    'u' as it was with every other FormField fixed the issue.
    <SharePoint:FormField runat="server" id="ff1{$Pos}" ControlMode="Edit" FieldName="Esittaja" __designer:bind="{ddwrt:DataBind('u',concat('ff1',$Pos),'Value','ValueChanged','ID',ddwrt:EscapeDelims(string(@ID)),'@Esittaja')}"
    />
    Explanation:
    DataBind operation type parameters (the first parameter) are listed below:
    'i' stands for INSERT,
    'u' stands for UPDATE,
    'd' stands for DELETE.
    http://webcache.googleusercontent.com/search?q=cache:d9HHY4I7omgJ:thearkfloats.blogspot.com/2014/03/sharepoint-2010-data-source-control.html+&cd=4&hl=en&ct=clnk&gl=in
    If this helped you resolve your issue, please mark it Answered

  • Not able to use Commit after the function module STATUS_OBJECT_CREATE

    I am using function module   STATUS_OBJECT_CREATE
       CALL FUNCTION 'STATUS_OBJECT_CREATE'
              EXPORTING
               CHGKZ         = 'X'
               CLIENT        = SY-MANDT
                OBJNR         = LV_OBJNR3
                OBTYP         = 'IWE'
                STSMA         = 'ZS_RE_01'
              IMPORTING
                OBJNR         = LV_OBJNR3.
                STONR                        = LV_STONR.
            IF SY-SUBRC = 0.
                COMMIT WORK.
            ENDIF.
    i am getting error after the COMMIT WORK .
    I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
    Category               ABAP Programming Error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    ABAP Program           SAPLBSVU
    Application Component  CA-GTF-TS-SMT
    Date and Time          03/17/2014 07:01:29
    |Short text                                                                                        |
    |    The ABAP/4 Open SQL array insert results in duplicate database records.                       |
    |What happened?                                                                                    |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "SAPLBSVU" had to be terminated because it has                       |
    |    come across a statement that unfortunately cannot be executed.                                |
    |What can you do?                                                                                  |
    |    Note down which actions and inputs caused the error.                                          |
    |                                                                                                  |
    |                                                                                                  |
    |    To process the problem further, contact you SAP system                                        |
    |    administrator.                                                                                |
    |                                                                                                  |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
    |    at and manage termination messages, and you can also                                          |
    |    keep them for a long time.                                                                    |
    |Error analysis                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                 |
    |     in                                                                                           |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING                    |
    |     clause.                                                                                      |
    |    Since the caller of the procedure could not have anticipated that the                         |
    |    exception would occur, the current program is terminated.                                     |
    |    The reason for the exception is:                                                              |
    |    If you use an ABAP/4 Open SQL array insert to insert a record in                              |
    |    the database and that record already exists with the same key,                                |
    |    this results in a termination.                                                                |
    |                                                                                                  |
    |    (With an ABAP/4 Open SQL single record insert in the same error                               |
    |    situation, processing does not terminate, but SY-SUBRC is set to 4.)                          |
    |How to correct the error                                                                          |
    |    Use an ABAP/4 Open SQL array insert only if you are sure that none of                         |
    |    the records passed already exists in the database.                                            |
    |                                                                                                  |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                     |
    |                                                                                                  |
    |    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"                                              |
    |    "SAPLBSVU" or "LBSVUU01"                                                                      |
    |    "STATUS_UPDATE"                                                                               |
    |                                                                                                  |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                                  |
    |    1. The description of the current problem (short dump)                                        |
    |                                                                                                  |
    |       To save the description, choose "System->List->Save->Local File                            |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    2. Corresponding system log                                                                   |
    |                                                                                                  |
    |       Display the system log by calling transaction SM21.                                        |
    |       Restrict the time interval to 10 minutes before and five minutes                           |
    |    after the short dump. Then choose "System->List->Save->Local File                             |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    3. If the problem occurs in a problem of your own or a modified SAP                           |
    |    program: The source code of the program                                                       |
    |       In the editor, choose "Utilities->More                                                     |
    |    Utilities->Upload/Download->Download".                                                        |
    |                                                                                                  |
    |    4. Details about the conditions under which the error occurred or which                       |
    |    actions and input led to the error.                                                           |
    |                                                                                                  |
    |    The exception must either be prevented, caught within proedure                                |
    |    "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in                  |
    |     the                                                                                          |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                 |
    |System environment                                                                                |
    |    SAP Release..... 702                                                                          |
    |    SAP Basis Level. 0010                                                                         |
    |                                                                                                  |
    |    Application server... "sds6ci"                                                                |
    |    Network address...... "11.224.101.53"                                                         |
    |    Operating system..... "Linux"                                                                 |
    |    Release.............. "2.6.18-194.el5"                                                        |
    |    Hardware type........ "x86_64"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                 |
    |    Work process number.. 17                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "gctsdb01lds.hsi.hugh"                                                     |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "DS6"                                                                      |
    |    Database user ID.. "SAPDS4"                                                                   |
    |                                                                                                  |
    |    Terminal.......... "GCTEMP02VDI"                                                              |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                         |
    |    created (date)... "Sep 14 2013 05:28:14"                                                      |
    |    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"                              |
    |    Database version. "OCI_102, 10.2.0.5.0, V2, default"                                          |
    |                                                                                                  |
    |    Patch level. 500                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
    |    SAP database version. 720                                                                     |
    |    Operating system..... "Linux 2.6, Linux 3"                                                    |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 1317248                                                                              |
    |    EM...... 0                                                                                    |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 1242912                                                                              |
    |    MM Free. 53400                                                                                |
    |User and Transaction                                                                              |
    |    Client.............. 160                                                                      |
    |    User................ "DV018458"                                                               |
    |    Language key........ "E"                                                                      |
    |    Transaction......... "SE38 "                                                                  |
    |    Transaction ID...... "5323C30FC9364665E10000000BE06533"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "SAPLBSVU"                                                               |
    |    Screen.............. "RSM13000 3000"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE".                     |
    |    The main program was "RSM13000 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 60                                  |
    |    of the (Include) program "LBSVUU01".                                                          |
    |    The program "SAPLBSVU" was started in the update system.                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                   |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor                |
    |     declared                                                                                     |
    |    in the RAISING clause of its signature.                                                       |
    |                                                                                                  |
    |    The procedure is in program "SAPLBSVU "; its source code begins in line                       |
    |    1 of the (Include program "LBSVUU01 ".                                                        |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   30|  LOOP AT jsto_upd WHERE chgkz = 'X'.                                                       |
    |   31|    CHECK: jsto_upd-chgnr > '000',                                                          |
    |   32|           jsto_upd-stsma NE jsto_upd-stsma_old.                                            |
    |   33|    CLEAR jcdo_tab.                                                                         |
    |   34|    MOVE-CORRESPONDING jsto_upd TO jcdo_tab.                                                |
    |   35|    MOVE-CORRESPONDING chdat    TO jcdo_tab.                                                |
    |   36|    jcdo_tab-stsma_new = jsto_upd-stsma.                                                    |
    |   37|    APPEND jcdo_tab.                                                                        |
    |   38|  ENDLOOP.                                                                                  |
    |   39|* Änderungen zu Einzelstatus (Insert)                                                       |
    |   40|  LOOP AT jest_ins WHERE chgkz = 'X'.                                                       |
    |   41|    CHECK jest_ins-chgnr > '000'.                                                           |
    |   42|    CLEAR jcds_tab.                                                                         |
    |   43|    MOVE-CORRESPONDING jest_ins TO jcds_tab.                                                |
    |   44|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   45|    jcds_tab-chind = 'I'.                                                                   |
    |   46|    APPEND jcds_tab.                                                                        |
    |   47|  ENDLOOP.                                                                                  |
    |   48|* Änderungen zu Einzelstatus (Update)                                                       |
    |   49|  LOOP AT jest_upd WHERE chgkz = 'X'.                                                       |
    |   50|    CHECK jest_upd-chgnr > '000'.                                                           |
    |   51|    CLEAR jcds_tab.                                                                         |
    |   52|    MOVE-CORRESPONDING jest_upd TO jcds_tab.                                                |
    |   53|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   54|    jcds_tab-chind = 'U'.                                                                   |
    |   55|    APPEND jcds_tab.                                                                        |
    |   56|  ENDLOOP.                                                                                  |
    |   57|* Verbuchung Statusobjekte                                                                  |
    |   58|  DESCRIBE TABLE jsto_ins LINES sy-tabix.                                                   |
    |   59|  IF sy-tabix > 0.                                                                          |
    |>>>>>|    INSERT jsto CLIENT SPECIFIED                                                            |
    |   61|                FROM TABLE jsto_ins.                                                        |
    |   62|  ENDIF.                                                                                    |
    |   63|  DESCRIBE TABLE jsto_upd LINES sy-tabix.                                                   |
    |   64|  IF sy-tabix > 0.                                                                          |
    |   65|    field-symbols <fs_jsto_line> like jsto_upd.                                             |
    |   66|    loop at jsto_upd assigning <fs_jsto_line>.                                              |
    |   67|      IF <fs_jsto_line>-chgnr = '000'.                                                      |
    |   68|        <fs_jsto_line>-chgnr = '999'.                                                       |
    |   69|      ENDIF.                                                                                |
    |   70|* on change of status profile delete user status related to old profile                     |
    |   71|      IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.                                  |
    |   72|        DELETE FROM JEST CLIENT SPECIFIED WHERE                                             |
    |   73|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   74|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   75|               STAT  LIKE 'E%'.                                                             |
    |   76|        DELETE FROM JCDS CLIENT SPECIFIED WHERE                                             |
    |   77|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   78|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   79|               STAT  LIKE 'E%'.                                                             |

    i tried with out using commmit but it is not creating Status.
    When i see the function module help and they are trying to COMMIT
    FU STATUS_OBJECT_CREATE
    Short Text
    Create Status Object
    Functionality
    The function module generates a status object.
    Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
    If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
    Example
    Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        objnr = objektnummer
        obtyp = 'ORC'
        stsma = 'STATSCHEM'.
    commit work.
    Creating the same order with a temporary object number
    data: objectkey like ionra.
    * TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
    objectkey-aufnr = '100123'.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        i_objectkey = objectkey
        obtyp       = 'ORC'
        stsma       = 'STATSCHEM'.
      importing
        objnr       = objektnummer.
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer_neu.
    call function 'STATUS_OBJECT_SWITCH_NUMBER'
      exporting
        objnr_old = objektnummer
        objnr_new = objektnummer_neu.
    commit work.
    Notes

  • Shopping cart not in sourcing cockpit after PO qty been reduced

    Hi ,
    We have a issue where a shopping cart was created with qty 100 and it came to sourcing cockpit.PO was then created for the shopping cart with the value qty 100. Later GR and Invoice was done for against the PO for quantity 25. PO qty was then reduced to 25. But still the shopping cart has not come back to the sourcing cockpit.
    Table BBP_PDIGP shows the following value for the item of the shopping cart :
    VAL ASN E = 0
    VAL ASN = 0
    VAL CF E = 25
    VAL CF    =          0.00
    VAL CF     =         0.00
    VAL IV E       =     25.00
    VAL IV       =       0.00
    VAL PO E        =    0.00
    VAL PO E AGG     =   0.00
    QUAN ASN E      =    0.000
    QUAN ASN      =      0.000
    QUAN CF E =          25.00
    QUAN CF       =      0.000
    QUAN IV E    =       25.00
    QUAN IV        =     0.000
    QUAN PO E  =        25.00
    NUM ASN      =       0
    NUM CONF     =       0
    NUM INV     =        0
    SOURCE REL IND = blank
    My questions are :
    1) Root cause of the issue ? Scenario where this can happen ?
    2 ) How to resolve the issue ? Just changing the SOURCE REL IND to X does not suffice (Tried the FM BBP_PDIGP_DB_DIRECT_UPDATE to set the sourcing indicator ) . Only when I clear all the values shown above to zero (change the values from 25 to 0) , does the shopping cart comes to sourcing cockpit . But the SC come with the qty 100 which is not correct , it should be 100- 25 = 75.
    Please suggest and pls answer all the questions.
    REgards,
    Saurav

    Hi
    as of now ,
    if the deletion of purchase order can make shopping cart item available in the cockpit.
    but you can not expect the sc item should goes to cockpit if the PO quantity has been reduced .
    In the PDP scenario - SAP suggested some custom logic if the quantity increased in the PR and remaining item comes / shows in the cockpit but no sap never provide any solution for quantity REDUCED.
    Muthuraman
    The above is my experience but you can check with SAP what is the standard.

  • How to update the editor properly after the source types change??

    Dear all;
    i'm using LLBLgen tools (o/r mapper tools) which helps me to create my BLL layer;
    recently i have upgraded from vs 2008 to vs 2013 and i got the following  bug :
    strange thing i have noticed is that if i tried to make any changes in db and updated it in llbl application then visual studio (after clean and rebuild the solution ) recognize changes only in the code behined editor but in the design editor if i
    tried to put gridview control and tried to populate it using LLBLdataSource control  then the gridview control load old fields not the new ones
    why this problem keep happening in the design editor but fixed in the code behind????
    so i tried to post this bug in LLBLgen forums and i got the following response :
    " the datasource controls sometimes act weird because vs.net doesn't update the editor properly after the source types change. This is unfortunately a problem related to the ASP.NET tooling for webforms.."
    so  any idea on how to fix this issue
    thanks
    Tamer El Morsi

    As your issue is related to ASP.NET and web forms, I suggest you visit the Microsoft ASP.NET site (link below) and post in a topical forum there:
    http://forums.asp.net/

  • Problem on PC: During import, I can locate the sources folder however the photo do not display. Was working fine.

    Problem on PC: During import, I can locate the sources folder however the photo do not display. Was working fine. All file types, Lightroom is no longer recognising the images to import, The panel that usually displays them remains empty.  Try using backup versions, removing software that could conflict , still no joy, has anyone had this problem?

    Did you follow this procedure?
    Our iTunes guru Terence Devlin advises the following:
    1. Quit iTunes
    2. Drag the iTunes folder from your internal hd - located in ~/Music folder - to your external hd. DO NOT delete the original one from your internal hd... yet!
    3. When the transfer is complete, press and hold the Option(alt) key and fire up iTunes.
    4. A "Choose iTunes Library" window will come up. Click on the "Choose Library" button.
    5. Navigate to where the iTunes folder is located in the external hd.
    6. Within the iTunes folder, select the iTunes Library file and click Choose...
    That's it. iTunes will now display all your playlists, songs, movies, podcasts etc. At this point, should you wish, you can delete the iTunes folder from the internal hd to free up space.
    More info:
    http://support.apple.com/kb/HT1751
    Or if you prefer a more complicated explanation:
    http://www.ilounge.com/index.php/articles/comments/moving-your-itunes-library-to -a-new-hard-drive

  • Recently, after cancelling the tick of a song, which is the next song after the one I am listening, in the song list, the canceled song will still run for the next song. I remember that it used not to happen like this. How can I solve this problem?

    Recently, after cancelling the tick of a song, which is the next song after the one I am listening, in the song list, the canceled song will still run for the next song. I remember that it used not to happen like this. How can I solve this problem?

    This looks like a change of behaviour in iTunes 12. Once songs are queued up to the Up Next list then they play whether ticked or not. If you want to skip certain songs already queued click the Up Next tool, then click the small X to the left of the song that appears when you hover over it.
    tt2

  • I have updated iOS7 today via iTunes as I was not able to update it directly in the iPhone. After the update I restored the back up and now the iPhone is not getting started. Please advice?

    I have updated iOS7 today via iTunes as I was not able to update it directly in the iPhone. After the update I restored the back up and now the iPhone is not getting started. Please advice?

    That error message suggest you have a permissions issue. Make sure you have full read/write privileges for the Drive/ Folder location that you are copying the files to. 

  • The project file is not bound to source control, but the solution contains source control binding information for it.

    This may be more of a SQL Server Management Studio question, but I couldn't find a SSMS forum...
    I've got a database solution that contains several projects.  They're just to keep track of changes to stored procedures, triggers, views, etc in a few databases I maintain.  There is a problem with two of the projects though.  No matter what I do, I can't seem to get them bound to source control right.  When I open the solution, I get:
    The project file is not bound to source control, but the solution contains source control binding information for it.
    With two options, use solution binding and remove solution binding.  If I keep the solution binding, everything works fine.  But it's really annoying to have to deal with every time I open the solution.  If I remove the solution binding, the projects are now unbound again.  If I try to fix them (using the change source control or Add Selected Projects to Source Control options under the File->source control menu), I just end up in the same situation.  I've even tried deleting the projects and re-creating them from scratch, then re-adding them to VSS.  If I open the solution files in a text editor I can see the SCC tags in every project, but these two.  Since I can't manually add the tags, and Management Studio itself only seems to want to bind them the wrong way, I'm getting really frustrated.
    Can anyone point me toward a way to bind these so they work like the rest?

    However, that does not appear to be the ONLY cause of the problem.  I am a single user and only using TFS2010 and SSMS2008R2.  My issue is that I wanted a solution file for each project so that they could managed independently, and a super-solution
    file that contained all projects, so that I could perform system-wide searches and cross-checks.
    I solved the problem by:
    1. Choosing the option to use solution binding, then
    2. Adding another project to the solution.  This forced the re-write of the solution file.
    3. Adding another script to the project.  This forced the re-write of the project file.
    4. Checking in all changes.
    5. Deleting the new script and the extra project,
    6 Checking in all changes.
    This appears to have solved the problem.

  • When you turn on the ipad2 it does not start up properly.  The rotating disk that happens when you turn off the ipad appears after the apple logo comes up

    When you turn on the ipad2 it does not start up properly.  The rotating disk that happens when you turn off the ipad appears after the apple logo comes up during start-up and stays there for ten minutes.  Then, the ipad will start up properly.

    Have you tried a reset ? Press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.

Maybe you are looking for