Creating Routings Operations using BAPI_ROUTING_CREATE

Hello,
I am creating Routing operations using BAPI_ROUTING_CREATE. The parameters which I am using are:
PROFILE
TASK
MAT_ALLOC
OPERATIONS.
The group counter and group are given internal number assignment.
In my case for 1 material number plant combination only 1 task exist. This can be considered as Header record. For this Header record there are multiple operations. My program calls BAPI only When any combination of MATNR or WERKS changes in MAT_ALLOC. It works fine for 1 operation but fails incase of multiple operations. The error is routing material assignment does not exist. I have checked for all madatory parameters in FM documentation. The BAPI when executed independently works fine but in program it fails.File format is
Mat. No. Plant Key Date Status Usage Operation Number Work center Control Key Description val unit.
I am calling BAPI only when Mat no or plant changes.Unitl then I append the data in internal tables.
Passing the data in this format every operation is given Mat No and Plant, then y it is giving error routing material assignment does not exist.
Please help in this regard.
Thanks
Khushboo

Well actually that´s almost exactly what my task is as well.
So what i do is:
- reading the headdata of the given routing (the one which is to be copied)
- reading the positiondata of the given routing (the one which is to be copied)
then calling the BAPI_ROUTING_CREATE while exporting the headdata and the positiondata to the BAPI.
It works perfect for the routing itself, but the BAPI doesnt create any operations while it displays a sucess message and NO errormessages.

Similar Messages

Upload Multiple Operation using BAPI_ROUTING_CREATE

Sir,
I have to upload routing operation using this BAPI_ROUTING_CREATE. I have created a upload program for that.
I have collect the data in Task, material and Operation table. They have multiple line item against One Material.
but after executing this bapi gives this type of error.
E
Create task list: Consistency check was not successful
A
For further processing, the routing entry is missing.
So Please Guide me how to do this.
Data :
Multiple Operation have One Material.
Thanks!
Ram

Well actually that´s almost exactly what my task is as well.
So what i do is:
- reading the headdata of the given routing (the one which is to be copied)
- reading the positiondata of the given routing (the one which is to be copied)
then calling the BAPI_ROUTING_CREATE while exporting the headdata and the positiondata to the BAPI.
It works perfect for the routing itself, but the BAPI doesnt create any operations while it displays a sucess message and NO errormessages.

Create Routing Groups using BAPI_ROUTING_CREATE Limitation?

Hi all,
I am doing a conversion for the routing groups for PP. The routing groups include sequence, operation number, material assigned and component allocation.
In this project, the BOM size of the material is super huge, thus to ease the conversion. I have used Function module to download the BOM structure and then allow user to maintain manually the operation and sequence. After that I will use BAPI BAPI_ROUTING_CREATE to do the conversion.
And I manage to get all operation, sequences, material assigned and component allocated. However, I face a problem as the BOM size keep increasing and same material BOM might be assigned to different header BOM at the same time. Thus, key field such as level and path is important for the input.
Note: Please check the order path in CA03, the technical name is STPOB-WEGXX1 with attribute type DEC length 4.
In my case, the Order Path is more than 99... around few hundreds.... But the issue is the order path field used in the BAPI_ROUTING_CREATE: BAPI1012_COM_C-ORDER_PATH is only has attribute type NUMC length 2.
Either I get a short dump by passing in the order path, or I might miss out the some component allocation using the BAPI. Anyone faces this before? Please advise.
Thanks.
Best regards,
Vin

Hi Vivek,
I got this reply from SAP.
ORDER_LVL and ORDER_PATH need not be filled, but PATH has to be
filled with the KANTE values.
The logic to calculate path value is the same as the kante value.
(PATH)
A (N) 0
-> B (P) 1
-> B1(N) 1
-> B2(P) 2
-> C (P) 3
-> C1 (N) 3
-> C2 (P) 4
N- normal item P- phantom
Note 305919 details this.
However, it quite confuses me as I read through sapnote 305919 : It seems like what is been replied from SAP does not really correct.
Symptom
You want to create component allocations to phantom assemblies using batch or direct input. In order to uniquely identify the phantom assembly, you must enter the level and the path. This note describes how the SAP System assigns the level and the path.
Thus, I will continue to check with SAP. I think this is the inconsistency of the database and the BAPI, correct me if I am wrong.
Thanks a lot.
Regards,
Vin

The new ibook app and ibook update is designed for iPhone 5 operating system. When my iPhone4 recently updated the ibook app, it created many problems using the ibook to download and read my books. Can I get the previous ibook app back on my phone.

The new ibook app and ibook update is designed for iPhone 5 operating system. When my iPhone4 recently updated the ibook app, it created many problems using the ibook to download and read my books. Can I get the previous ibook app back on my phone.

Check your trash can on the desktop. The old version is automatically moved to the trashcan. You should be able to move it from the trashcan back to the Apps folder within the iTunes folder. The update that was pushed out was for iBooks to work with iOS 7 not iPhone 5. iOS 7 was released today.

Using BAPI_ROUTING_CREATE to copy routing from legacy system

Hi,
I would like to know whether its possible to use BAPI_ROUTING_CREATE in my Routing conversion program to upload all routing data from the legacy system into SAP?
It's kind of urgent.
Thanks in advance

Well actually that´s almost exactly what my task is as well.
So what i do is:
- reading the headdata of the given routing (the one which is to be copied)
- reading the positiondata of the given routing (the one which is to be copied)
then calling the BAPI_ROUTING_CREATE while exporting the headdata and the positiondata to the BAPI.
It works perfect for the routing itself, but the BAPI doesnt create any operations while it displays a sucess message and NO errormessages.

Creating Routings via LSMW

Hi all,
Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
I need to add PRT's material assignments and long texts to the routing.
Any help greatly appreciated.

Hi,
Use standard batch/Direct input : RCPTRA02
Source Fields
        MATERIAL_ROUTING          Material
            PLNAL                          C(002)    Group Counter
            MATNR                          C(018)    Article Number
            WERKS                          C(004)    Site
            OPERATION_ROUTING         Operations
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                STEUS                          C(004)    Control Key
                ARBPL                          C(008)    Work center
                WERKS                          C(004)    Site
                LTXA1                          C(040)    Operation short text
                MEINH                          C(003)    Quantity unit for operation (batch input)
                BMSCH                          C(017)    Base quantity (Batch input)
                LAR02                          C(006)    Activity Type
                VGE02                          C(003)    Unit for the standard value (batch input)
                VGW02                          C(011)    Standard Value (Batch Input)
                LAR03                          C(006)    Activity Type
                VGE03                          C(003)    Unit for the standard value (batch input)
                VGW03                          C(011)    Standard Value (Batch Input)
            COMPONENT_ROUTING         Components
                PLNAL                          C(002)    Group Counter
                VORNR                          C(004)    Operation/Activity Number
                POSNR                          C(004)    BOM Item Number
                MATNR                          C(018)    Article Number
                WERKS                          C(004)    Site
Field Mapping and Rule
       RC271_DS                       Work center structure for direct input (for datasets)
           Fields
               TCODE                        Transaction Code
                                   Rule :   Constant
                                   Code:    RC271_DS-TCODE = 'CA01'.
               STTAG                        Character Field Length = 10
                                   Rule :   Constant
                                   Code:    RC271_DS-STTAG = '18.03.2014'.
               AENNR                        Change Number
               REVLV                        Revision Level
               WERKS                        Site
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
               PROFIDNETZ                   Profile
               PLNNR                        Key for Task List Group
               PLNAL                        Group Counter
                                   Rule :   Transfer (MOVE)
                                   Code:    RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
               STATU                        Status
                                   Rule :   Constant
                                   Code:    RC271_DS-STATU = '4'.
               VAGRP                        Responsible Planner Group/Department
                                   Rule :   Constant
                                   Code:    RC271_DS-VAGRP = 'KD1'.
               VBELN                        Sales Document
               POSNR                        Character field of length 6
               PSPNR                        Work Breakdown Structure Element (WBS Element)
MAPL_DI_DS                     Assign routing to article for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    MAPL_DI_DS-ACTTYP = 'H'.
        MATNR                        Article Number
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        LIFNR                        Vendor Account Number
        KUNR                         Account Number of Customer
        SUCHFELD                     Search Field for Customer-Specific Task List Selection
        VBELN                        Sales Document
        POSNR                        Sales Document Line Item (Batch Input Field)
        PSPNR                        Work Breakdown Structure Element (WBS Element)
PLKO_DI_DS                     Header structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLKO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
        VERWE                        Use by user or system
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VERWE = '1'.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
        STATU                        Status
                            Rule :   Constant
                            Code:    PLKO_DI_DS-STATU = '4'.
        PLNME                        Unit of measure for the task list (batch input)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-PLNME = 'KG'.
        LOSVN                        From lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSVN = '0'.
        LOSBS                        To lot size (BTCI)
                            Rule :   Constant
                            Code:    PLKO_DI_DS-LOSBS = '999999999'.
        VAGRP                        Responsible planner group/department
                            Rule :   Constant
                            Code:    PLKO_DI_DS-VAGRP = 'KD1'.
        KTEXT                        Task list description
                            Rule :   Constant
                            Code:    PLKO_DI_DS-KTEXT = 'Article Routing'.
        TXTSP                        Single-Character Indicator
PLPO_DI_DS                     Routing/item structure for direct input (for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Code:    PLPO_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLPO_DI_DS-PLNFL = '000000'.
        VORKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
        UVOKN                        Node number (batch input)
        UVORN                        Suboperation
        STEUS                        Control key
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
        ARBID                        Object ID (batch input)
        OBJTY                        Object types of the CIM resource
        ARBPL                        Work center
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
        WERKS                        Site
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
        KTSCH                        Standard text key
        LTXA1                        Operation short text
                            Rule :   Transfer (MOVE)
                            Code:    PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
MEINH                        Quantity unit for operation (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
UMREN                        Denominator for conversion from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREN = '1'.
UMREZ                        Numerator for converting from unit to base unit (BTCI)
                    Rule :   Constant
                    Code:    PLPO_DI_DS-UMREZ = '1'.
BMSCH                        Base quantity (Batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
ZMERH                        Break time (batch input)
ZEIER                        Unit for break time (batch input)
LAR01                        Activity Type
VGE01                        Unit for the standard value (batch input)
VGW01                        Standard Value (Batch Input)
LAR02                        Activity Type
VGE02                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
VGW02                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
LAR03                        Activity Type
VGE03                        Unit for the standard value (batch input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
VGW03                        Standard Value (Batch Input)
                    Rule :   Transfer (MOVE)
                    Code:    PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
PLMZ_DI_DS                     Article component allocation for direct input(for datasets)
    Fields
        ACTTYP                       Processing type for objects to be imported
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-ACTTYP = 'H'.
        PLNAL                        Group Counter
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
        PLNFL                        Sequence
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-PLNFL = '000000'.
        PLNKN                        Node number (batch input)
        VORNR                        Operation/Activity Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
        STLTY                        BOM category
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLTY = 'M'.
        STLNR                        Bill of material
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLNR = '00000005'.
        STLAL                        Alternative BOM
                            Rule :   Constant
                            Code:    PLMZ_DI_DS-STLAL = '01'.
        STLKN                        Node number (batch input)
        POSNR                        BOM Item Number
                            Rule :   Transfer (MOVE)
                            Code:    PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
WERKS                        Site
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
BOMAT                        Article Number
                    Rule :   Transfer (MOVE)
                    Code:    PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
STLST                        Order level
STLWG                        Order path
STLTY_W                      BOM category
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLTY_W = 'M'.
STLNR_W                      Bill of material
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLNR_W = '00000005'.
STLAL_W                      Alternative BOM
                    Rule :   Constant
                    Code:    PLMZ_DI_DS-STLAL_W = '01'.
Map the extra fields according to your requirement. Hope you'll find the code helpful.

KEY LOOKUP Operator using TCL

Hi,
I am trying to create a key lookup operator using tcl.
OMBALTER MAPPING 'TESTMAP' ADD KEY_LOOKUP OPERATOR 'INSTITUTION_CHARACTERISTIC_DIM'\
SET PROPERTIES (BOUND_NAME,CREATE_NO_MATCH_ROW, LOOKUP_CONDITION)VALUES
('INSTITUTION_CHARACTERISTIC_DIM','true','OUTGRP1.INSTITUTION_CHAR_SRCKEY
= INGRP1.INST_CHAR_SRCKEY')
and then adding an attribute to the INGRP
OMBALTER MAPPING 'TESTMAP'ADD ATTRIBUTE 'LAST_ACTIVITY_DATE' OF GROUP 'INGRP1' OF OPERATOR 'INSTITUTION_CHARACTERISTIC_DIM'
This is creating a key lookup operator by the name
INSTITUTION_CHARACTERISTIC_DIM, and i can see the Bound Name in the
properties window, but when i double click and open the key lookup, i
dont see the result table under the LOOK UP tab.Because of this, the
attributes dont get added in the OUTGRP of the key lookup.
Am i missing some important property of a key look up?
can some one please help me with this...
Thanks in advance...

Hi,
you have to bind the lookup operator to the table:
OMBALTER MAPPING 'MAP_LOOKUP' ADD KEY_LOOKUP OPERATOR 'MY_LOOKUP' BOUND TO TABLE '/MY_PROJECT/MY_DB/DIM_CUSTOMERS'
OMBALTER MAPPING 'MAP_LOOKUP' MODIFY OPERATOR 'MY_LOOKUP' SET PROPERTIES (CREATE_NO_MATCH_ROW, LOOKUP_CONDITION)VALUES ('true','OUTGRP1.ID_CUSTOMER=INGRP1.ID_CUSTOMER')
OMBALTER MAPPING 'MAP_LOOKUP' ADD ATTRIBUTE 'ID_CUSTOMER' OF GROUP 'INGRP1' OF OPERATOR 'MY_LOOKUP'Regards,
Carsten.

Creation of routing using BAPI_ROUTING_CREATE

Hi,
I need to create routing using BAPI. I am using BAPI_ROUTING_CREATE. My routing is not saved. I am using BAPI_TRANSACTION_COMMIT also when message type is 'S', after Routing is created. But Still my routing is not saved. I can see successfull message as N/50003801/01 is created .
I already spent lot of time on this, and gone thru coding available in google search, still no use. I debug BAPI couple if timings but didnot find anything.
I even tried using SE37 directly by Sequence execution of both BAPI_ROUTING_CREATE & BAPI_TRANSACTION_COMMIT, no use. i tried different combinations like by giving input values to INPUT PARAMETERS OF BAPI_ROUTING_CREATE giving BOM usage, without BOM usage, TESTRUN value as 'X' and as SPACE.
I even gone thru this Func. Module /SAPMP/BAPI_ROUTING_PROCESS which directly calls BAPI_ROUTING_CREATE inside it, but no use. I see many people is giving solution as BAPI_TRANSACTION_COMMIT, but I really think that is not problem.
Does any one have any idea on this issue.
Thanks in Advance

Hi Cthota,
Indeed, TESTRUN must be equal to space. And BAPI_TRANSACTION_COMMIT is needed, as stated in the doc's.
Could you please check all messages in RETURN table? Very likely there is something not correct in the parameters, that do not prevent the system to assign routing numbering, but that may affect saving.
Just let us known...
Bye,
flavio

How to create business operation for starting workflows

How to create business operation for starting workflows from worklist?
When I call methods that implements business operation from java class everything
works fine(wlpi-ejb.jar is required), but when I call business operation from
Studio I can't use classes from wlpi-ejb.jar.

Business operation is called by WLIS. So, I include wlpi-ejb.jar into WLIS classpath.
Studio uses deployed EJB from wlpi-*.jar, I don't know why Studio doesn't see
methods from deployed EJBs when WLIS classpath contains wlpi-ejb.jar.
"Andrew Pitonyak" <[email protected]> wrote:
>
When studio starts, what is your classpath? If you use the included batch
file to start it, then your class path may not include this :-)
Andrew
"Raul" <[email protected]> wrote in message
news:[email protected]..
How to create business operation for starting workflows from worklist?
When I call methods that implements business operation from java classeverything
works fine(wlpi-ejb.jar is required), but when I call business operationfrom
Studio I can't use classes from wlpi-ejb.jar.

A few months ago, I purchased a new iMac. I recently created a movie using iMovie. Then I found out that iDVD is not included. So I have the problem that I want to burn a movie that I can play on my DVD player and watch on a television. i rang Applecare a

A few months ago, I purchased a new iMac. I recently created a movie using iMovie. Then I found out that iDVD is not included. So I have the problem that I want to burn a movie that I can play on my DVD player and watch on a television. I rang Applecare and was told that I need a program called BURN.
Is this correct? I can export the movie from iMovie in a m4v format, but I think I need to convert this to iso format before I can burn the disc.
I know there are programs like TOAST that will do this, but it is expensive.
I would be very grateful for any assistance.

Burn will not do what you want, and there is no real substutute for iDVD.
Why is there no iDVD on my new Mac?
Apple insists that the entire world has access to fast broadband (and are prepared to pay for the considerable bandwidth usage) and wants to distribute home movies to friends and relatives via download (iCloud, YouTube, Facebook, whatever) rather than mailing them a DVD. The fact that in reality not all users do, has so far had no effect on this policy. If you scream and shout loudly enough down the phone Apple may send you a free copy of iDVD. Stating that they would return their brand new Mac unless they received a copy of iDVD worked for some, but that is now said to have been withdrawn by Apple.
Also, you can complain bitterly via Apple’s Feedback link, perhaps suggesting that Apple could have provided a choice between burning DVDs and distributing home movies by other means. You may feel that Apple should not dictate how you destribute family videos or photos to distant relatives and friends, and should not assume that every user is prepared to pay for the excessive bandwidth usage charged by ISPs for huge downloads from the App Store:
http://www.apple.com/feedback/
Whilst Macs with a Superdrive continue to be able to burn video DVDs, the software for so doing, iDVD, is no longer included in the iLife bundle that came with OS 10.7 Lion (which also omitted iWeb) or that comes with OS 10.8 Mountain Lion. And it is no longer included in the iLife 11 from the online Apple Store: http://www.apple.com/ilife/. Your only solution is to look on Amazon or eBay and try to get an older version that includes iDVD 7, i.e. iLife version 9 onwards. You should also do this if you plan to buy a new Mac anytime soon, as stocks of iLife that include iDVD will not be available for ever.
However, the vastly more expensive FCPX can burn a DVD without iDVD or DVD Studio Pro involvement, but lack the themes etc of iDVD. Also, of course, there is Roxio Toast, which is the best software for burning anything but again does not offer the flexibility of iDVD.
And if you think Microsoft are any better, their new Windows 8 operating system will not play DVDs, or burn them, unless customers buy an extra upgrade, the company has announced: http://www.gizmag.com/windows-8-no-dvd-playback/22443/
In other words, computer manufacturers have declared optical media as dead, long before consumers are ready to stop using them, which is fine as long as they offered us a choice, but they won’t even do that. Flexibility and intuitive use of a computer seems to be a thing of the past.

HOW TO CREATE PURCHASE ORDER USING BAPI

HI FRIENDS,
I HAVE URGENT REQUIREMNT ,TO CREATE PURCHASE ORDER USING BAPI.PLS HELP ON THIS.
UR'S
RAVI

Hi
See the sample code and do accordingly
REPORT zpo_bapi_purchord_tej.
DATA DECLARATIONS *
TYPE-POOLS slis.
TYPES: BEGIN OF ty_table,
v_legacy(8),
vendor TYPE bapimepoheader-vendor,
purch_org TYPE bapimepoheader-purch_org,
pur_group TYPE bapimepoheader-pur_group,
material TYPE bapimepoitem-material,
quantity(13),
delivery_date TYPE bapimeposchedule-delivery_date,
net_price(23),
plant TYPE bapimepoitem-plant,
END OF ty_table.
TYPES: BEGIN OF ty_alv,
v_legs(8),
success(10),
v_legf(8),
END OF ty_alv.
TYPES: BEGIN OF ty_alv1,
v_legf1(8),
v_msg(500),
END OF ty_alv1.
*-----Work area declarations.
DATA: x_table TYPE ty_table,
x_header TYPE bapimepoheader,
x_headerx TYPE bapimepoheaderx,
x_item TYPE bapimepoitem,
x_itemx TYPE bapimepoitemx,
x_sched TYPE bapimeposchedule,
x_schedx TYPE bapimeposchedulx,
x_commatable(255),
x_alv TYPE ty_alv,
x_alv1 TYPE ty_alv1,
x_alv2 TYPE ty_alv1.
*-----Internal table declarations.
DATA: it_table TYPE TABLE OF ty_table,
it_commatable LIKE TABLE OF x_commatable,
it_item TYPE TABLE OF bapimepoitem,
it_itemx TYPE TABLE OF bapimepoitemx,
it_sched TYPE TABLE OF bapimeposchedule,
it_schedx TYPE TABLE OF bapimeposchedulx,
it_alv TYPE TABLE OF ty_alv,
it_alv1 TYPE TABLE OF ty_alv1,
it_alv2 TYPE TABLE OF ty_alv1.
DATA: po_number TYPE bapimepoheader-po_number,
x_return TYPE bapiret2,
it_return TYPE TABLE OF bapiret2,
v_file TYPE string,
v_temp(8),
v_succsount TYPE i VALUE 0,
v_failcount TYPE i VALUE 0,
v_total TYPE i.
DATA: v_temp1(5) TYPE n VALUE 0.
DATA: x_event TYPE slis_t_event,
x_fieldcat TYPE slis_t_fieldcat_alv,
x_list_header TYPE slis_t_listheader,
x_event1 LIKE LINE OF x_event,
x_layout1 TYPE slis_layout_alv,
x_variant1 TYPE disvariant,
x_repid2 LIKE sy-repid.
DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
SELECTION-SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
*-----To fetch the flat file.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK v_b1.
AT SELECTION-SCREEN *
AT SELECTION-SCREEN.
IF p_file IS INITIAL.
MESSAGE text-001 TYPE 'E'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*-----To use F4 help to find file path.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
v_file = p_file.
START-OF-SELECTION *
START-OF-SELECTION.
PERFORM gui_upload.
LOOP AT it_table INTO x_table.
PERFORM header_details.
v_temp = x_table-v_legacy.
LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
PERFORM lineitem.
PERFORM schedule.
ENDLOOP.
DELETE it_table WHERE v_legacy = v_temp.
PERFORM bapicall.
MOVE po_number TO x_alv-success.
APPEND x_alv TO it_alv.
CLEAR x_alv.
*-----To clear the item details in internal table after the operation for a header.
REFRESH: it_item,
it_itemx,
it_sched,
it_schedx.
CLEAR: v_temp1.
ENDLOOP.
v_total = v_succsount + v_failcount.
PERFORM display_alv.
FORM GUI_UPLOAD *
FORM gui_upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = v_file
filetype = 'ASC'
TABLES
data_tab = it_commatable
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17
IF sy-subrc = 0.
*-----To fetch the comma seperated flat file into an internal table.
LOOP AT it_commatable INTO x_commatable.
IF x_commatable IS NOT INITIAL.
SPLIT x_commatable AT ',' INTO
x_table-v_legacy
x_table-vendor
x_table-purch_org
x_table-pur_group
x_table-material
x_table-quantity
x_table-delivery_date
x_table-net_price
x_table-plant.
APPEND x_table TO it_table.
ENDIF.
CLEAR x_table.
ENDLOOP.
ENDIF.
ENDFORM. " gui_upload
FORM HEADER_DETAILS *
FORM header_details .
MOVE 'NB' TO x_header-doc_type.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-vendor
IMPORTING
output = x_table-vendor
MOVE x_table-vendor TO x_header-vendor.
MOVE x_table-purch_org TO x_header-purch_org.
MOVE x_table-pur_group TO x_header-pur_group.
x_headerx-doc_type = 'X'.
x_headerx-vendor = 'X'.
x_headerx-purch_org = 'X'.
x_headerx-pur_group = 'X'.
ENDFORM. " header_details
FORM LINEITEM *
FORM lineitem .
v_temp1 = v_temp1 + 10.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = v_temp1
IMPORTING
output = v_temp1.
MOVE v_temp1 TO x_item-po_item.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-material
IMPORTING
output = x_table-material.
MOVE x_table-material TO x_item-material.
MOVE x_table-quantity TO x_item-quantity.
MOVE x_table-net_price TO x_item-net_price.
MOVE x_table-plant TO x_item-plant.
x_itemx-po_item = v_temp1.
x_itemx-material = 'X'.
x_itemx-quantity = 'X'.
x_itemx-net_price = 'X'.
x_itemx-plant = 'X'.
APPEND x_item TO it_item.
APPEND x_itemx TO it_itemx.
CLEAR: x_item, x_itemx.
ENDFORM. " lineitem1
FORM SCHEDULE *
FORM schedule .
MOVE x_table-delivery_date TO x_sched-delivery_date.
MOVE v_temp1 TO x_sched-po_item.
x_schedx-delivery_date = 'X'.
x_schedx-po_item = v_temp1.
APPEND x_sched TO it_sched.
APPEND x_schedx TO it_schedx.
CLEAR: x_sched, x_schedx.
ENDFORM. " schedule
FORM BAPICALL *
FORM bapicall .
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = x_header
poheaderx = x_headerx
IMPORTING
exppurchaseorder = po_number
TABLES
return = it_return
poitem = it_item
poitemx = it_itemx
poschedule = it_sched
poschedulex = it_schedx.
IF po_number IS NOT INITIAL.
v_succsount = v_succsount + 1.
MOVE x_table-v_legacy TO x_alv-v_legs.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
v_failcount = v_failcount + 1.
MOVE x_table-v_legacy TO x_alv-v_legf.
MOVE x_table-v_legacy TO x_alv1-v_legf1.
LOOP AT it_return INTO x_return.
IF x_alv1-v_msg IS INITIAL.
MOVE x_return-message TO x_alv1-v_msg.
ELSE.
CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
ENDIF.
ENDLOOP.
APPEND x_alv1 TO it_alv1.
CLEAR x_alv1.
ENDIF.
ENDFORM. " bapicall
FORM DISPLAY_ALV *
FORM display_alv .
PERFORM x_list_header.
PERFORM build_fieldcat CHANGING x_fieldcat.
x_repid2 = sy-repid.
x_event1-name = 'TOP_OF_PAGE'.
x_event1-form = 'TOP_OF_PAGE'.
APPEND x_event1 TO x_event.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = x_fieldcat
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_save = 'A'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " display_master_data
FORM USER_COMMAND *
FORM user_command USING ucomm LIKE sy-ucomm selfield
TYPE slis_selfield.
READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
CLEAR : x_alv2,it_alv2[].
LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
x_alv2 = x_alv1.
APPEND x_alv2 TO it_alv2 .
ENDLOOP.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
CLEAR : x3_fieldcat,it_fieldcat[].
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_LEGF1'.
x3_fieldcat-reptext_ddic = text-111.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_MSG'.
x3_fieldcat-reptext_ddic = text-112.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
x_layout1-colwidth_optimize = 'X'.
x_layout1-zebra = 'X'.
IF it_alv2[] IS NOT INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = it_fieldcat
i_save = 'A'
i_callback_top_of_page = 'TOP'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv2
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDIF.
ENDFORM.
FORM USER_COMMAND *
FORM top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = 'Commentry'.
ENDFORM.
FORM BUILD_FIELDCAT *
FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
DATA: x1_fieldcat TYPE slis_fieldcat_alv.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '1'.
x1_fieldcat-fieldname = 'V_LEGS'.
x1_fieldcat-reptext_ddic = text-108.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '2'.
x1_fieldcat-fieldname = 'SUCCESS'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-109.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '3'.
x1_fieldcat-fieldname = 'V_LEGF'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-110.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
ENDFORM. " build_fieldcat
FORM BUILD_LIST_HEADER *
FORM x_list_header.
DATA: x_list_header1 TYPE slis_listheader.
*-----List Header: type H
CLEAR x_list_header1 .
x_list_header1-typ = 'H'.
x_list_header1-info = text-105.
APPEND x_list_header1 TO x_list_header.
*-----List Key: type S
x_list_header1-typ = 'S'.
x_list_header1-key = text-106.
x_list_header1-info = v_total.
APPEND x_list_header1 TO x_list_header.
*-----List Key: Type S
CLEAR x_list_header1 .
x_list_header1-typ = 'S'.
x_list_header1-key = text-107.
x_list_header1-info = v_succsount.
APPEND x_list_header1 TO x_list_header.
ENDFORM. " build_list_header
FORM TOP_OF_PAGE *
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = x_list_header.
ENDFORM. " TOP_OF_PAGE
Reward points if useful
Anji

Using Adobe Premier Elements to create a video using the photos and it is make the photos blurry. Is there a setting to correct this?

as the subject states, i am suing Premier Elements pro to create a video using photos. The photos are clear then when you play the video they become blurry. I would guess there would be a way to correct this but not having much success. any helps would be great.

Iltowman
Thanks for the follow up. Right now I see details that do need addressing. For one, you are importing 3:2 photos into a project set for 16:9.
You still have not told us what version of Premiere Elements that you are using and on what computer operating system it is running. For now I will assume, Premiere Elements 13/13.1 on Windows 7, 8, or 8.1 64 bit. NTSC setup.
Please try the following as a mini test run (just a few of your photos) to determine if the Timeline photos present better in the Edit area and in an export.
1. Open Premiere Elements 13/13.1 to the Expert workspace and go to File Menu/New/Project and Change Settings.
2. In Change Settings, change the settings to
NTSC
DSLR
1080p
DSLR [email protected]
OK out of there.
3. In the New Project Dialog that now opens, rename the project and make sure that you have a check mark next to Force Selected Project Setting on This Project. OK out of there.
4. Back in the Export workspace, import your photos using Premiere Elements' Add Media/Files and Folders/Projects Assets from where you drag the photos to the Timeline. There will be an orange line over the Timeline content. Press the Enter key of the computer main keyboard. or the Render button above the Timeline to do Timeline rendering which will result in the best possible preview in the Edit area monitor.
Also, right click the Edit area monitor, select Playback Quality, and then determine if the "Highest" gives better results than "Automatic".
If all looks good, then let us look at the quality of a AVCHD.mp4 export of that Timeline....
Publish+Share
Computer
AVCHD
with Presets = MP4 - H.264 1920 x 1080p30.
Is the quality of the photos in this mini test run better, the same, or worse?
About your photos (3872 x 2592 3:2)...video is 4:3 or 16:9. So to avoid black borders, you could consider
a. cropping the originals from 3:2 to 16:9 before import
or
b. importing them as is and doing any needed scaling in the Edit area monitor
But, right now the focus is on image clarity rather than black borders.
Please review and consider.
Thank you.
ATR

Creating aVirtual directory Using java

Hai ,
I am Using windows XP Operating system, I know how to create a directory using java,
can you please suggest me a procedure to create a virtual(web share ) directory using java.
waiting for your reply
Thanks & Regards,
Naga Raju

Virtual Programmer is in the to share the directory
over the Internet.No, that's a file/web server. :) I see, it's a Microsoft term.

No ability to create PDF Files using Acrobat 6.01_6.06 after installing Word 2010. (Windows XP)

Since installing Word 2010 (upgrading from Word 2003) there are no visable PDF Icons nor ability to create PDF Files using Adobe Acrobat 6.06. Operating system is Windows XP. Browser is IE8. Various attempts to bypass this situation have not been successful. No problems had been experienced earlier using Acrobat 6.01 through 6.06 with Word 2003 and earlier Word versions during the passed 10 years or so. Adobe's support is not responding to recognize mentioned situations, nor is there any a solution to fix the problem. Low volume small businesses,with limited need to create PDF files, are being considerably burdened to substante a $200 investment to upgrade to Acrobat X, which may as well not be the solution. It is appealed for Adobe Forums readers to share similar experiences with possible fixes at hand. Responses will be greatly appreciated. Thank you...

Your response is greatly appreciated, Bernd...
Unfortunately, those of us who milk software packages for eons such as
Acrobat 6.06 Standard, a full version of Acrobat X is quoted to be $299
with no ability to upgrade since 7.0 is the cutoff which remains to be
only $139.
It seems to me, Military personal, retired or just ole toots who did
their think, would offer considerations such as Staples, Lowe's, and
other big boxes offer. Such is greed for some who do not consider
alternatives above their noses...
Thank you,
Skip

Sync and Create project operation from DTR is taking more than one hour

Hi All.
Recently basis team has implemented the track for ESS/MSS application.So When we import the track to NWDS its showing 500 Dcs.
I have successfully done the Sync and create project operation from DTR for 150 DCS and its take 5 min per Dcs.
However after that when i am trying to sync Dc or create project DC from DTR the operation is taking more than 3 hour per DC.Which should not be the case because for rest 150 DC that i ahve done Sync operation adn Create project operation from DTR it hardly takes 5 min per Dc.As this operataion is taking so much time finally i have close the NWDS to stop this operation.
I am using NWDS 2.0.15 and EP7.0 portal SP15 and NWDI is 7.0
Can any body tell how to solve this issue so that i can Sync and Create project from DTR for a DC within 5 min?
Thanks
Susmita

Hi Susmita,
If the DCs are fine in CBS build, then I feel there is no need to test all of them locally in NWDS.
You can verify some certain applications in these DCs, then you sync & create project for these DCs & test run these applications.
As I get you only need to check ( no changes will be done ), yes you can verify them in small groups (say 20-25 DCs/group) in different workspaces so that no workspace is overloaded.
But why do you want to keep a copy of them locally as you are not making any changes, you can Unsync & Remove these projects once verified & use the same workspace to work on the next set of DCs.
Hope this clarifies your concerns.
Kind Regards,
Nitin
Edited by: Nitin Jain on Apr 23, 2009 1:55 PM

Creating Routings Operations using BAPI_ROUTING_CREATE

Similar Messages

Maybe you are looking for