Possible status of a mobileconfig?

what are the possible status of a mobileconfig? and what do they mean exactly?
what i have are: unsigned, unverified and verified. Any other possibilities?
I have a mobileconfig file that created by myself and now it shows unverified. How do I make it verified? is it because the certificate i am using is not from what they have installed on the phone?
thx for any hints
CJ

Unsigned - The mobileconfig is not signed by anyone. Therefore the source is unknown.
Unverified - The mobileconfig is signed, but the source is not recognized as trusted.
Verified - The mobileconfig is signed and is recognized as a trusted source.
You are correct. The reason that your mobileconfig file does not appear as "Verified" is because the required certificates are not installed on the iPhone. In order to appear as a "verified" source the mobileconfig file must be able to be verified up to the root certificate (i.e. you may need to install more than just one certificate).

Similar Messages

  • XI IDoc Acknowledgement - Acknowledgement not possible status

    Hi Experts,
    My scenario:
    SAP IDOC - XI - jdbc (oracle)
    Problem:
    Getting the infamous "Acknowledgement not possible" status in SXI_MONI. I only need the transport acknowledgements back to SAP not the application acknowledgements. The messages themselves route fine from source to destination.

    check if this blog helps you:
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    From the blog:
    The system acknowledgement sent by the file adapter is converted into an ALE audit message and sent
    back to the sender SAP system by an IDOC ACK channel configured in XI(an IDOC receiver adapter).
    For your info:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    Edited by: abhishek salvi on May 15, 2009 10:48 AM

  • Generation possible status not changing

    hi,
    I created the SOP report from specification work bench. I can view the report entry in report management  but the status of the report is in " generation possible" it is not getting executed to the next status. Nor is the report getting released .
    I can view the report  output from specification workbench 'report from template' .
    For this I created a new generation variant with the validity area and application object assigned to it.
    All the ticks relevant are done in generation variant
    My report template is also in released status.
    Please suggest !
    Ashish

    Hello
    I totally agree to Anil.  "Generation possible" is a "bad" status. To my knowlegde as explained by Anil these are "potential" reasons:
    - RFC conncetion lost
    - WWI Server not ready and up; or to many requests are there (I realized this this week): Therefore the WWI process ist still working but the number of documents to be generated is high and therefore it can happen that the WWI server needs 8 or more hours to handle all requests. Afterwards (if you are lucky) the reports in the queue have been generated sucessfully.
    In any case: to my knowledge if non of the "normal" reasons apply and could be removed you need the "debug/replace" option because you will not be able to get this stupid report processed to the next stage. I assume that you will find some OSS notes regarding this (as mentioned by Anil) and may be in higher EH&S release (ECC 6) a "better" solution is found.
    With best regards
    C. B.
    Edited by: Christoph Bergemann on Feb 6, 2010 7:21 PM
    PS: With ECC 6.0 and Enhancement Pack 3 further technical options exist in controlling the WWI process.
    PPS: a quick research in the area of WWI in OSS I found something like 12 potential OSS Notes regarding this issue
    Edited by: Christoph Bergemann on Feb 6, 2010 7:22 PM
    Edited by: Christoph Bergemann on Feb 6, 2010 7:23 PM
    Edited by: Christoph Bergemann on Feb 6, 2010 7:24 PM
    Edited by: Christoph Bergemann on Feb 6, 2010 7:28 PM

  • Possible to display more statuses in the PO search screen?

    Hello,
    When you search for purchase orders, you can select between many statuses.
    You can search for orders in status "outstanding confirmations" by selecting this status in the dropdown and you will get all POs that are in this status in a list.
    Problem/question is, the status shown pr order in the status column is "ordered" and not "outstanding confirmations". This goes for other statuses as well
    Question is why it is working this way, and if it is possible to do anything with this?
    rgds
    GAR

    Hi
    <b>Looks like a bug in the system.. Which SRM version are you using ?</b>
    <u>Please see some other related SAP OSS Notes -></u>
    Note 827638 - Populate possible statuses for PO correctly in extraction
    Note 940159 - Deleted Purchase Order has wrong status
    Note 824410 - Change PO extractor to populate correct status
    Note 870584 - Implementation of note 782729 fails.
    Re: Confimation in status I1017
    Note 890812 - Inbound EDI message ORDRSP: Cancelling a purchase order item
    Note 995086 - PO Confirmation is Sent as Rejected
    Note 562226 - SRM-SUS: PO rejected for SUS MM
    Note 411601 - Deleted confirmation displayed incorrectly in purch.order
    <u>Hope this will help. Do let me know in next reply.</u>
    <b>Incase this does not help, also raise a Customer OSS message with SAP as well.</b>
    Regards
    - Atul

  • EBP purchase order status is comming as blank from last 5 months

    Hi,
    Advance thanks for BW experts.
    Here is the issue I am facing.
    We are extracting shopping cart data from EBP(SRM) daily.
    We are using Data source as '0BBP_TD_PO_1' in SRM.
    In BW it is coming to ODS '0BBP_PO' for collecting data.
    Info source we are using is '0BBP_PO_TD_1'.
    The problem is EBP(SRM) Purchase order status coming as blank from last 5 months, we are using every thing standard objects, no routine, i checked in BW side. I found that purchase order status field coming as blank from SRM. It seems to some problem in extractor?.
    If any one experts in SRM-BW please help me on this how to proceed?.
    for more information PO status filed (InfoObject) in BW is -0bbp_PROPO

    hi,
    take a look sap oss note 827638
    check also 824410,809118
    827638
    Symptom
    Status is blank
    Other terms
    0BBP_TD_PO_1, PO extractor, I1016, Status rejected
    Reason and Prerequisites
    The rejected status is not considered while extraction
    Solution
    Got a mail from customer regarding all the possible statuses which is not populated while extraction.
    Status   Populated or not ?
    Ordered                                             X
    Awaiting Approval                                  X
    In Your Inbox
    Release Rejected
    Held                                                X
    Deleted                                             X
    Outstanding Confirmations Outstanding Invoices
    Transfer Failed                                    X
    Confirmed by Vendor
    Partly Confirmed by Vendor
    Rejected by Vendor
    Changes Transmitted Obviously we dont report on all these statuses in BW but release rejected might be an important status and BATA (customer no: 169433) needs this status to be extracted through the PO extractor. I am changing the extractor code for this status. In future we can enhance this note to take care of other statuses relevant for BW. For now other statuses seems to be not usufull for BW reporting.

  • Status Definition in Project Administration

    Hi@ll
    i want to know, if you define Status in the PROJECT_ADMIN then this statuses will be available at diffrent locations, e.g. Business Blueprint Documents, Configurations Documents etc.
    For example, i define 5 status: open, closed, in work, paused, reopened
    All them will be shown everywhere i can set a status!
    So, if i want e.g. at a business process description dcument only two status: open and in work; can i define this? or will i always be able to choose of all status at e.g. business process description dcument???
    i hope you understand this.
    thx
    Marco

    Hi Marco,
    The status values you define at SOLAR_PROJECT_ADMIN aren't meant to be available for Documents you upload, they are for other tabs/reasons, including the following:
    (1) As a possible Status value in SOLAR_PROJECT_ADMIN itself, in General Data tab
    (2) Admin Tab of SOLAR01/ 02
    For Status Values for Documents, you have to make settings in Configuration as follows:
    SPRO
    SAP Solution Manager  -> Configuration -> Scenario-specific settings -> Cross-scenario settings -> Document Management -> Status for Documents
    You may also like to read other nodes and what they stand for. They are very useful indeed - provided the project is ready to let the SolMan Consultant gather requiremetns and do a proper job. Many of them cannot be (should not be) done in a hurry
    Trust this answers; please feel free to pose any other question on this.
    Best regards,
    Srini

  • Confirmation status I1016 release rejected

    Hi SRM gurus,
      We are working on classic scenario on SRM 5.0. We created a shopping cart, PO and confirmation.
    We have the status of the confirmation as I1016 release rejected when we do the conf. from EBP. If we do the GR in the backend the conf. is updated.
    For all PO's the EBP conf. is not transfered to the backend. We tried to run the clean req req report manually. We tried to search thru the OSS notes and also thru this forum but could not find worthy info.
    Can any one suggest what could be possible reasons?
    We have our workflow working fine with the status as approved. If we try to replicate the same manually with the BBP_PD_CONF_GETDETAIL it gives the same status.
    Is there any way to change the status of the conf. so that it will be updated in the backend.
    Workflow conditions are working perfect as there is no workflow error also.
    Best regards,
    Sridhar.

    Hi
    Please try this ->
    The status of the Rejected shopping cart can be seen under Stats : head.
    You can see the status in CRM_JEST table using the GUID of the shopping cart.
    The status will be updated with I1016 (Release rejected) from I1015 (Awaiting approval).
    Also look in the transaction - bbp_pd .
    See related Notes ->
    Note 958297 Search for confirmations with transfer errors
    Note 537459 Confirmation cannot be reversed despite invoice quantity = 0
    Note 1073012 Search for Confirmations with Status 'All'
    Note 1014108 No DocB status change after SRM document is rejected
    Note 827638 Populate possible statuses for PO correctly in extraction
    Hope this makes you clear. Clarifications are welcome.
    Regards
    - Atul

  • Reg: Function Module thats used to check the status of JOBS and mail it

    Hi Experts,
    Is there any Standard Function module thats going to find the status of the jobs and mail this status to specied email ID in .xls format. While checking status function module should give whether job is - Aborted, Successful, Running, Waiting, Locked, Error, Warning, Starting Date, Ending Date of the Job.
    Please help me,

    Hello Nagaraj,
    You can find out the status of a job with the SHOW_JOBSTATE function module. You provide this function module with a job name and job number. It returns one of the six possible statuses of the job:
    ABORTED TYPE C,
    FINISHED TYPE C,
    PRELIMINARY TYPE C,
    READY TYPE C,
    RUNNING TYPE C,
    SCHEDULED TYPE C.
    Following is the link for the same:
    http://help.sap.com/saphelp_sm32/helpdata/en/fa/096e10543b11d1898e0000e8322d00/content.htm
    Warm Regards,
    Riki Dash

  • Yellow status in front of idoc

    What means yellow status in front of idoc . (Green means it is processed, Red means it is in error).
    Where to find reason it is yellow

    Jan
    Try tcode we05. F4 help on "Current Status" will give you  possible status of all the IDocs. From the status of IDoc you can determine where it is stucking.
    If you know the IDoc number then it will easier for you to determine its state ( WE05).. Which status your IDocs in?
    Also check BD87..
    Edited by: Anindya Bose on Aug 10, 2009 5:41 PM

  • Status on a PO

    Hello All -
    I know this seems like a simple question but does anyone have a list of the possible statuses when processing a shopping cart all the way through to invoice?  I have a purchase order that has been received and invoiced but the statuses that are showing on the Header System Status tab are:
    Complete
    Created
    Document Complete
    Ordered
    Should there be a change in the system status when the goods are received and when the invoice is received?  It seems like my statuses are not getting updated.  I am running BBP_GET_STATUS_2. The goods receipt and the invoice receipt numbers from ECC are getting replicated into SRM. 
    We are in SRM 5.0. 
    Thanks
    Jane

    Hello Jane,
    The status of the PO will always be as you have listsed earler, once a PO is created in SRM and successfully replicated to ERP system
    Now if you do GR or IR the PO status will not get changed.
    But for the Shopping cart items you can view that the in the Table   BBP_PDIGP is updated with the below fields:
    Value of Entered Confirmations
    Entered Invoice Value
    Quantity of Entered Confirmation
    Entered Invoiced Quantity
    Quantity of POs/Confirmations/Invoices Created
    Regards,
    Hiten

  • Indoc status 64

    i m new to ale idoc n created 2 clients 800(sender system) and 810(reciever system)
    all connections are well i got status message 03 and 30 and 01 and 12 in 800 .
    in client 810 i m getting
    status 64 "immediate processing not possible"
    status 50 "idoc ready to transfer"
    status 64 "incorrect parameter with call function"
    sender system idoc is posted but at inbound error occurrs .. i check function everything is ok ..
    we20 both the partner profile are active
    how to solve error .. ?

    There could be so many reasons for that. Anyway , try processing the Idoc using RBDAPP01 and check if it goes to 51/53. If it goes to 51 , check the error message in the previous status record. You will get an idea.
    Regards,
    Deepthi

  • Status in order management

    hi
    when i read the oracle material i saw these many statuses in header and lines of order management.I request some one in this forum to explain when each statuses occurs or give us some link for reference.
    The below is the list
    Order Header Statuses
    Following is a list of all possible statuses assigned to an order header.
    • Active
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Start Date
    • Booked
    • Cancelled
    • Closed
    • Customer Accepted
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Expired
    • Internal Approved
    • Internal Rejected
    • Invoice Interface - Complete
    • Lost
    • Offer Expired
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Submitted
    • Terminated
    • User Working
    Order Line Statuses
    Following is a list of all possible statuses assigned to an order line.
    • Awaiting Export Screening
    • Awaiting Fulfillment
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Invoice Interface - Partially Interfaced, RFR Item
    • Awaiting Invoice Interface - Pending Complete Delivery
    • Awaiting Invoice Interface - RFR Item
    • Awaiting Invoice Interface - Unexpected error
    • Awaiting Payment Assurance - On Hold
    • Awaiting Payment Assurance - Receipts Not Assured
    • Awaiting Receipt
    • Awaiting Reprice - Invalid setup
    • Awaiting Reprice - On reprice line hold
    • Awaiting Reprice - Pricing error
    • Awaiting Reprice - Unexpected error
    • Awaiting Return
    • Awaiting Return Disposition
    • Awaiting Shipping
    • Awaiting Supply
    • BOM and Routing Created
    • Booked
    • Cancelled
    • Closed
    • Completed Export Screening
    • Config Item Created
    • Customer Accepted
    • Data Error Export Screening
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Fulfilled
    • Interfaced to Receivables
    • Internal Approved
    • Internal Rejected
    • Inventory Interfaced
    • Invoice Interface - Not Applicable
    • Lost
    • Offer Expired
    • PO-Created
    • PO-Partial
    • PO-Received
    • PO-ReqCreated
    • PO-ReqRequested
    • Partially Interfaced to Receivables
    • Payment Assurance - Complete
    • Payment Assurance - Incorrect Data
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Picked
    • Picked Partial
    • Preprovision
    • Preprovision Failed
    • Preprovision Requested
    • Preprovision Succeeded
    • Production Complete
    • Production Eligible
    • Production Open
    • Production Partial
    • Provisioning Failed to update Transaction Details
    • Provisioning Rejected
    • Provisioning Requested
    • Provisioning Successful
    • Provisioning in Error
    • Released to Warehouse
    • Reprice - Complete
    • Reprice - Not Applicable
    • Returned
    • Scheduled
    • Shipped
    • Supply Eligible
    • Supply Open
    • Supply Partial
    • Third Party Billing Failed
    • Third Party Billing Requested
    • Third Party Billing Succeeded
    Regards
    sudharshan

    Hi Sudharshan,
    Probably this link will explain you to the most
    http://oracleappsdna.com/2011/07/sales-order-line-status-flow/
    Also any status codes are part of some lookups. You can get a bit more information of the status in Lookup Description.
    Thanks,
    Shailender

  • PLM7.02: Status & Release Management/ Status and Action Management

    Hello,
                    I´d like to know if anybody worked with Status & Release Management. And has some example to how we can customize: SAM (Status and Action Management) in “Define Status Scheme” transaction.
                    How it´s works the relationship with: Status: Attributes, Status: Field values, Scheme Definition, Attributes: Definition.
                    I´ll appreciated if you could give me a simple example of this functionality.
                    Thanks in advance.
                    Best Regards from Brazil.
                    Rodrigo Arai

    Hi Rodrigo,
    in a nutshell:
    - you can define status network based on objects (w.g. material)
    - Define Attributes: you can define attributes like DELETION_ALLOWED or LOCKED_FOR_CHANGE and you can implement preconditions in custom classes when should it happen
    - Define Status Field: you can define some fields which are related to the status. e.g. in recipe management RCP_USAGE
    - Status: you can define the different statuses (e.g. in process, completed..) with attributes
    - Scheme Definition: you can define the logic between statuses. E.g. you would like to swith from status In Process to Completed and from New to In Process. Then switching from New to Completed is not possible for the user.
    - Subobject Type Scheme only applied if you have subobjects
    here you can find the customizing documentation, there are some examples as well:
    Define Status Scheme
    Use
    In this Customizing activity, you define statuses and status schemes for object types and corresponding attributes.
    For each status, you can define which attributes are allowed to be set for an object with this status assigned.
    The status scheme defines the initial status and the possible transitions from one status to another.
    Activities
    You define status schemes as follows:
    1. Select the required object type and enter the following:
    a) An identifier
    b) An object type class (Note: this class should implement the interface class)
    c) A subobject type search help
    The search help provides a list of all possible subobject types. This feature enhances the usability while  maintaining status schemes at subobject-type level.
    d) If the
    Status
    tab page shall be visible on the PLM Web UI, select the
    Status Tab
    checkbox
    Status and action management is a reusable object. It has been modeled as a dependent object. The prerequisites to enable status and action management for any new objects are:
    Add the Status and Action Management tab page on the UI.
    Enable the Status Tab checkbox in this Customizing activity.
    2. Select the required object type and define the following attributes for it:
    a) An object type
    b) An attribute identifier
    c) An attribute description
    d) An attribute type
    e) Select a precondition class (Note: This class should implement the '/PLMB/IF_SAM_PRECONDITION' interface)
    3. Define the technical status field name.
    When you change the object status, the system updates the technical status field names to the new values made in these settings.
    4. Select object type and define corresponding statuses.
    a) Select the status and define the corresponding object type, an identifier, description, and status icon.
    Note:
    You cannot define new statuses for materials and material BOMs. For these objects, all values should be transferred from the back-end system.
    You can import the status values from the back-end system as follows:
    b) Select the object type that represents a material or a MatBOM.
    c) Select
    Status
    in the dialog structure.
    d) Choose the
    New Entries
    pushbutton.
    e) Choose the
    Import Status
    pushbutton.
    Note
    The system imports the following status values into SAM:
    For material: the
    X-plant matl status
    (cross-plant material status)
    For MatBOM: the header status
    Although you cannot change the imported value for a material or a MatBOM, you can change its name and description to conform to SAM terminology.
    You can differentiate between the following cases for objects whose status values are imported from the back-end system:
    The object was not created on the PLM Web UI, but in the back-end system; no SAM status scheme or status was assigned, but a status value was set in the back-end system.
    If you assign a SAM status scheme to this object later on that contains the equivalent imported status values, the SAM status value is set accordingly, even if any precondition check results of the SAM status scheme may exist.
    The object was created in the back-end system or on the Web UI and a SAM status scheme is assigned to the object on the PLM Web UI.
    If the corresponding status value is changed in the back-end system, then existing SAM preconditions for this status transition and allowed status transitions are checked. If the preconditions are not fulfilled, a message is raised and the new status cannot be saved.
    5. Specify which attributes are allowed for each object type when the chosen status is set.
    a) Select a status and open the
    Attributes
    screen.
    b) Choose an object type.
    c) Choose an attribute.
    6. Define whether values from other technical fields are affected by setting this status.
    a) Select a status and open the
    Field Values
    screen.
    b) Select an object type.
    c) Select a technical field name.
    7. Specify the status scheme. The status scheme defines the initial status and status transition for the object type. For example, below is a list of standard status schemes defined for iPPE object types.
    Assembly Header - PLM_PPEAH
    Assembly Item - PLM_PPEAI
    Product Item Variant - PLM_PPEPIV
    Product Variant - PLM_PPEPV
    You can also create schemes for the object type as follows:
    a) Specify an identifier and description for the status scheme and set one of the statuses defined above as the initial status.
    b) Select the status scheme and open the
    Transitions
    screen. Enter all possible status transitions by specifying the source (
    Status From
    ) and target status (
    Status To
    c) Select the
    Long Text
    checkbox if you want the system to open the long text editor on the
    Status
    tab in the PLM Web UI. You can use the long text editor to create notes for this transition.
    8. Define the scheme at subobject-type level by entering following parameters:
    a) Object type
    b) Subobject type (You can choose from the list of subobject types you have specified when defining the search help in step 1)
    Alternatively, you can define a default status scheme that is automatically displayed on the
    Status
    tab.
    The following statuses are included in the standard delivery:
    10 -  In Work
    20 - For Approval
    LINKED_DIR
    LINKED_MAT
    LOCKED_FOR_CHANGE
    REPLACE_PH_ASSEMBLY (only in the PLM_PPEAI assembly item and the PLM_PPEPIV product item variant)
    30 - Released For Planning
    LOCKED_FOR_CHANGE
    40 - Released
    RELEASED
    SUB_ITEM_STATUS
    The following status transitions are possible:
    FROM
    TO
    Long Text checkbox (dialog box for notes)
    10
    20
    20
    30
    30
    40
    20
    40
    20
    10
    X
    30
    10
    X
    40
    10
    X
    More on SAP help:
    Status and Action Management on the Web UI - SAP Library
    Best regards
    Tamas

  • Header and Line Statuses in OM

    hi
    Can any one give a brief on the below statuses in OM header and Line Level.
    The below is the list
    Order Header Statuses
    Following is a list of all possible statuses assigned to an order header.
    • Active
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Start Date
    • Booked
    • Cancelled
    • Closed
    • Customer Accepted
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Expired
    • Internal Approved
    • Internal Rejected
    • Invoice Interface - Complete
    • Lost
    • Offer Expired
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Submitted
    • Terminated
    • User Working
    Order Line Statuses
    Following is a list of all possible statuses assigned to an order line.
    • Awaiting Export Screening
    • Awaiting Fulfillment
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Invoice Interface - Partially Interfaced, RFR Item
    • Awaiting Invoice Interface - Pending Complete Delivery
    • Awaiting Invoice Interface - RFR Item
    • Awaiting Invoice Interface - Unexpected error
    • Awaiting Payment Assurance - On Hold
    • Awaiting Payment Assurance - Receipts Not Assured
    • Awaiting Receipt
    • Awaiting Reprice - Invalid setup
    • Awaiting Reprice - On reprice line hold
    • Awaiting Reprice - Pricing error
    • Awaiting Reprice - Unexpected error
    • Awaiting Return
    • Awaiting Return Disposition
    • Awaiting Shipping
    • Awaiting Supply
    • BOM and Routing Created
    • Booked
    • Cancelled
    • Closed
    • Completed Export Screening
    • Config Item Created
    • Customer Accepted
    • Data Error Export Screening
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Fulfilled
    • Interfaced to Receivables
    • Internal Approved
    • Internal Rejected
    • Inventory Interfaced
    • Invoice Interface - Not Applicable
    • Lost
    • Offer Expired
    • PO-Created
    • PO-Partial
    • PO-Received
    • PO-ReqCreated
    • PO-ReqRequested
    • Partially Interfaced to Receivables
    • Payment Assurance - Complete
    • Payment Assurance - Incorrect Data
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Picked
    • Picked Partial
    • Preprovision
    • Preprovision Failed
    • Preprovision Requested
    • Preprovision Succeeded
    • Production Complete
    • Production Eligible
    • Production Open
    • Production Partial
    • Provisioning Failed to update Transaction Details
    • Provisioning Rejected
    • Provisioning Requested
    • Provisioning Successful
    • Provisioning in Error
    • Released to Warehouse
    • Reprice - Complete
    • Reprice - Not Applicable
    • Returned
    • Scheduled
    • Shipped
    • Supply Eligible
    • Supply Open
    • Supply Partial
    • Third Party Billing Failed
    • Third Party Billing Requested
    • Third Party Billing Succeeded

    This information can be found in the Approvals Management implementation guide in metalink. The part number for this document is B31622-02
    Regards

  • Change Status Profile : User Status

    Hello Experts,
    We have created 14 User Status Values for Support Message in Solution Manager
    Status Profile: ZLFN0001 (Copy of SLFN0001) and modified to the requirements.
    Assigned this Status Profile to transaction type Zxxx
    Current settings:
    Status No.--Status-- Lowest -
    Highest -
    Trans.
    10--Status 01-1020--
    20--Status 02 -20--
    50 -
    INPR
    30--Status 03 -30--
    60 -
    INPR
    40--Status 04 -40--
    70 -
    INPR
    50--Status 05 -50--
    50 -
    FINI
    60--Status 06 -40--
    80 -
    INPR
    70--Status 07 -60--
    70 -
    FINI
    80--Status 08--80--
    91 -
    INPR
    90--Status 09--90--
    92 -
    INPR
    91--Status 10--60--
    91 -
    INPR
    92--Status 11--92--
    95 -
    INPR
    94--Status 12--94--
    94 -
    FINI
    95 -
    Status 13----9595--
    FINI
    96--Status 14--9696--
    FINI
    One of our requirements is that when the user status is Changed from "Status 08" to "Status 10", the only possible status available should be "Status 06" and the other statuses(07, 08 & 09) should be inactive or greyed out. Is there a possibility to hide status that is/are not required and the user should be able to see only 1 active status.
    What is the significance of Auth Code and Select Profile? Where do we assign Select profile to a Status Profile?
    Can anyone shed some light on this. Appreciate your response.
    Thanks,
    nancy

    Nancy, hi
    as far as I know, it is not possible to mark a status as inactive in certain cases.
    However, there might be a solution to your question:
    One ofcourse, is to change the order of the statuses so that you don't have to "skip" a status. For instance: switch status 8 with status 9, and change the properties of status 10 so that only status 9 can be reached (lowest status)
    The other option is to use authorizations on statuses, that's were the AUTH_KEY comes in. You can use the standard defined key, or you can create additional authorization keys.
    Let's say you create an additional key called Z_AUTH_1, and link this key to Status 08.
    An end user would then need to have this authorization key value in his role profile (object B_USERSTAT) to be able to set status 08.
    hope this answers your question.
    best regards,
    Jeroen.

Maybe you are looking for

  • Clearing GL accounts

    Hi, In the OBYC setting for the GR/IR clearing accounts, two different GL accounts was maintained for debit and credit posting. so the posting was entered in the resp GL account as per the Dr and Cr. Now when i tried to clear the GR/IR account thr'o

  • Dead screen during calls

    has anyone ran into this problem? I made a phone call and talked for a very short time, but as i went to hang up the call my screen was still black, i couldnt get the phone to responed, i pressed every button and touched the screen, it wouldnt respon

  • How to find and remove corrupted files?

    Hi, Can anyone give me some direction in locating and removing files that have been corrupted? I am trying to back up my system for the first time on time machine, and keep getting an error message. I visited an Apple store today for support and had

  • Java not loading

    Lion does not have a Java update available and I can not use a couple business platforms I need. anyone else having that same probblem and maybe have a solution? thanks! S2

  • A focus question: button activated by mouse or by ENTE

    In the following program: If the program is run as is ? The button can be activated only by the mouse. If the part: // try { // UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()); // catch(Exception e) { // e.printStackTrace(); is us