ME23N restrict IDOC creation and keep traffic light yellow

Hi,
I have a requirement in which I need to restrict the EDI IDOC if there are errors in the PO. Also as the IDOC is not created the messages (type NEU) should remain with the yellow traffic light as the IDOC is not processed. What would be the best approach to keep the traffic light yellow , I have identified the point to restrict IDOC creation but the traffic light is set to red.
Thanks,
Esha

Hello Esha,
I have identified the point tojavascript:; restrict IDOC creation but the traffic light is set to red.
Yellow light in Output type shows its Not Processed. If you are talking about exits EXIT_SAPLEINM_002/EXIT_SAPLEINM_011 they come into picture when Output type processing started. So ultimately they will have either Success/Error status.
Even by setting sy-msgty = 'W' in EXIT_SAPLEINM_002 and raising exception will not help.
You can play around with FMs mentioned in group WMCP and can check.

Similar Messages

Restrict IDoc creation by using deactivate change pointers

Hi Experts,
I am trying to restrict the creation of IDOCS by deactivate the change pointers from a ztable. if the record in ztable and BDCP table match then i should deactivate the change pointer. And restrict the creation of Idocs.
pls, suggest me soon... its urgernt.......
Regards,
CHK

Maybe using program RBDCPCLR to delete change pointers you don't want to use?

System status for IDOC creation and processing for production orders

All
I am creating IDOCs for production orders to send requirements to an external WM system for kitting execution.
I need to know whether there are any system statuses to notify me when an IDOC has been created,failed and processed. If not, how do I go about creating user defined statuses for these statuses.
Second question, which idocs should I use to confirm, teco and cancel the production orders from an external system?
Thanks
Evan

HI Evan
u can use the standard program - RBDMOIND scheduled in back ground to update the Idoc staus ,
this helps to update the IDoc Status from
'03 Data passed to port OK ' to
'12 Dispatch OK'
status 03 indicates the IDoc is successfully transmitted to Communication Layer and the Status 12 helps to confirm the data dispatch to the receiving port.

Suggestion for IDoc creation and conversion program

Hi Experts,
I want to send the data from SAP to Non-SAP System. The Non-SAP System needs the text file with delimiter.
So which way is better to send the data.
Via a IDOc with ALE OR
Just download the file by the program and send it to Non-SAP System.
Please suggest me, which option is best and cheapest and need the advantage and disadvantage for both the ways. And also how many hours will took to implement each scenarios.
As per my knowledge, The Idoc with ALE will took 3 Days to build the setup and prepare the IDoc and Conversion program will took 1.5 days to prepare the file.
Note:There are maximum 8 fields needs to send to the Non-SAP System from SAP. So not much information.
Thanks in Advance,
Warm Regards,
Vijay

Hi Gangisetty,
For less no. of fields transfer there is no need at all to go with ALE.
If there is some Standard Master Data to be transfered then IDOC comes very handy.
But if requirement is to fetch data from different tables and some formatting before sending to Legacy System then you should go with conversion Report which will fetch all required data, format or manipulate as per requirement and then using outbound control it can send the flat file Common Shared FTP folder.
Using Conversion Report which will required less development time and you can schedule it as per bussiness requirement.
Using ALE-IDoc may consume some time as you need to create Partner Profile, Logical System etc and it might be required to have PI(XI) as middleware for some internal formatting etc.
Though, Both ways are possible it's upto your call which way to go.
As per info given by you i would suggest to by Conversion Report Method.
Regards,
Vivek

System status or user status for IDOC creation and processing for prod ord

All
I am creating IDOCs for production orders to send requirements to an external WM system for kitting execution.
I need to know whether there are any system statuses to notify me when an IDOC has been created,failed and processed. If not, how do I go about creating user defined statuses for these statuses.
Second question, which idocs should I use to confirm, teco and cancel the production orders from an external system?
Thanks
Evan

For the first part of your query refer to the technical forums.
For the second part - refer to Idoc - LOIPRO01, it has a segment for Order status, that should be of interest.
Attn Moderators
I think it would be better to move this thread to a technical forum, so the requester can get the most relevant information.

IDOC creation and Processing

plz explain me how to create an IDOC for customer master and how to send to logical system

1)     IMG > Application Link Enabling (ALE) > Sending and Receiving > logical systems > Define Logical System: xxx
2)     IMG > Application Link Enabling (ALE) > Sending and Receiving > Systems in Network > Asynchronous Processing > Assigning Ports > Define Port:
The port need to be defined beneath FILE
The IDOC record types for SAP Release 4.x need to be selected
A physical directory is needed. One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
3)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
a)     Cross-System Company Codes
b) Assign Cross-System Company Code to Chart of Accounts
c) Assign Company Code to Cross-System Company Code
Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
4)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
5)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
6)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
Partner profile type/Partner type: LS logical system
Partner profile/Partner number: xxx
7)     BD12 Send Customers

USER EXIT FOR IDOC CREATION AND TRIGGER

I needed a user exit in which I could call my function module .The requirement is that whenever a sales order is created or changed ,on saving of the sales order I need to trigger an IDOC .Inside my function module I plan to use the MASTER_IDOC_DISTRIBUTE
Can anyone tell me if the above logic can work and please tell me the name of the user exit which I can use?

Hi
Instead of User exit, you can think of using SAP Standard Output type functionality.
Ask your functional consultant to create a Output type with Medium 6 and do the necessary outbound configuration in the Partner profile WE20 transaciton.
Regards
Madhan D
Edited by: Madhan Doraikannan on Dec 10, 2008 10:49 AM

Traffic lights - MRP

Can I change default traffic lights setting?
How?

Traffic Lights can be defined.
You can use the exception groups to define under which conditions materials are indicated by red, yellow, or green traffic lights. Example: You want all materials, whose dates lie in the past, to be indicated by a red traffic light.
The definition of traffic lights applies to both types of list.
Prerequisites-
You have accessed the material list in collective access, or the MRP list or stock/requirements list for a material.
In case of individual lists: you have displayed the material tree.
Procedure
1. Choose Green Dot
The system displays the Define traffic light dialog box.
2. Enter the number of workdays for the parameters Days' supply, 1st receipt days' supply and 2nd receipt days' supply, and under which circumstances the materials are to be displayed with red, yellow, and green traffic lights.
You want the traffic light to be red when the days' supply for a material is <= 0, yellow when the days' supply is > 0 and <= 10 days, and green when the days' supply is > 10 days.
Enter:
Color     Days supply
Red        0
Yellow     10
Green      999,9
4. Use the exception groups to define under which conditions materials are indicated by red, yellow, or green traffic lights.
You want materials with exception messages in exception group 4 to be indicated by a yellow traffic light and materials with exception messages in exception group 5 to be indicated by a red traffic light.
Choose:
                 Exception group 5          Exception group 5
Red                 X
Yellow                                                  X
Green
6. Save
Reward if cleared and close the thread.

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

Optical digital audio out - can I keep the light on?

I have my iMac hooked up to my Sony receiver with a TOSLINK optical cable.
I have noticed that the Mac shuts off the signal light if there has been no audio output for 15 seconds. My Sony receiver then goes into a sort of standby mode. When the iMac again outputs digital audio, it takes about a half second for the receiver to wake up from standby mode. So the first half second of any new audio output is clipped. This means that short things like alert sounds, trash empty sound, etc are not heard at all if there has been no other sound output for the last 15 seconds.
If there is a way to keep the light on all the time, then my receiver will always "hear" and output everything.
Is there anyway to do this? I have thought about making a ten second audio clip of silence, and having QuickTime or some other program continuously loop it. But there has to be a better way to keep the light on.

Answered. My latest Google search was successful.
I found a launch agent that uses the "say" command to "speak" a single space every 10 seconds. That keeps the audio system alive, and keeps the light on.
http://www.macupdate.com/info.php/id/29024/antipop

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

Mrp run and seeing the stock in md04 with green traffic light showing green

Hi,
i am running a mto scenario in which sale order is created and mrp run is done and i checked the stock md04 of a finished product in that the rawmaterials and semifinshed products are showing the traffic light green light of show overview tree in md04 when it is first time created there is no stock of the rawmaterial and semfinished product.
with out any stock why it is showing the traffic light green and what is the procedure to show the light red when stock is not there.
rawmaterial is of consumable like paint in which it is not supporting in the bom and it is giving the message it is of process material can any body pls help me how paint is created as a consumable in bom creation.
regards,
muralidhar.t

Hi muralidhar,
MRP is a planning tool, not an availability check one.
It means that you are getting a green light even though there's no stock because the lead time to procure is shorter than the requirement date.
Regarding consumables, I'm not sure what you include in that, but you can either define them as non stock items in the BOM (in which case they will be specifically purchased for the production order), or maybe you meant that these materials are planned using consumption based planning; in this case they are defined normally as a stock item in the BOM, the difference being that they are not exploded in MRP, and the requirements are not triggered by the higher level.
Regards,
Mario

IDoc Configuration for Production Order Creation and Change

Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal T

Hi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar

IDoc creation on save and change of production order

I am looking for a way to create, and send if possible (if not I'll send with a batch job), on the save (creation and change) of production orders. This will be a modified LOIPRO iDoc. Currently we have a customer exit on the save of the production order but because it is before the save we must predict the number of the prod order. This has worked but now we are creating one production order per line item in a sales order (automatically) so this is causing us to predict the same production order number twice. We need a way to automatically create and send an iDoc for all production orders for given plants. Right now the solution we are looking at is creating an output type and running through those output types a few times a day, sending them down to the Shop Floor system (proprietary system).
Is there anything setup in SAP that we can utilize?
Regards,
Davis

Hi Rick,
Follow the below sample steps for changing component quantity:
DATA:
    l_methods TYPE bapi_alm_order_method,
    it_boperations TYPE STANDARD TABLE OF bapi_alm_order_operation_e WITH HEADER LINE,
    it_components TYPE STANDARD TABLE OF bapi_alm_order_component_e WITH HEADER LINE,
    it_components1 TYPE STANDARD TABLE OF bapi_alm_order_component WITH HEADER LINE.
1. Call BAPI :BAPI_ALM_ORDER_GET_DETAIL , it will give existing order component details.
CALL FUNCTION 'BAPI_ALM_ORDER_GET_DETAIL'
    EXPORTING
      number        = <production order number>
    TABLES
      et_operations = it_boperations
      et_components = it_components
      return        = it_bapiret2.
2. Move it_components to components table compatibel to BAPI "BAPI_ALM_ORDER_MAINTAIN".
LOOP AT it_components.
MOVE-CORRESPONDING it_components TO it_components1.
_*"Note here while moving change the component quantity"*_
APPEND it_components1.
CLEAR it_components1.
ENDLOOP.
3. Build the methods table for change production order :
it_methods-refnumber = v_refnumber.
            it_methods-objecttype = 'COMPONENT'.
            it_methods-method = 'CHANGE'.
            it_methods-objectkey = v_objectkey.
            APPEND it_methods.
"Note v_refnumber has 1 to 1 relation ship with the components table, if you want to change First component in it_components1 then you have to enter value '1' here for v_refnumber.
it_methods-method = 'SAVE'.
        APPEND it_methods.
4 . Call
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
          TABLES
            it_methods   = it_methods
            it_component = it_components1
            return       = it_bapiret2.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

My MacBook Pro shut itself down and now it won't turn back on and the power light keeps flashing a green and amber but very dull. Help please!

My MacBook Pro shut itself down and now it won't turn back on and the power light keeps flashing the amber light. I don't know what to do, and this has never happened before.

Hello Toby135
Reset the SMC or System Management Controller to resolve issues with the power on your MacBook Pro and power adapter.
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/ht3964
Regards,
-Norm G.

ME23N restrict IDOC creation and keep traffic light yellow

Similar Messages

Maybe you are looking for