SAP ABAP Jobs with Verizon

Sap ABAP Technical Consultant Openings at Verizon ( MNC )—Hyd ( 3+ yrs relevant exp). Please find below the skill set.

No of Positions : Analyst - ( 3 + year )
: Sr Analyst - ( 4 + year )




About Project : Supply Chan Transformation project mainly deals with MM, Purchasing , Inventory Management modules. The resource need to have very good functional knowledge of MM, SD Modules.


They are currently looking for SAP ABAP Technical Consultant with Scripts, ALE, IDOC, Basic ABAP, Dialogue Programing and good functional knowledge.

Cross Application Knowledge is must and candidate should be working on permenant payroles.

read more...

Yahoo Software Development India Pvt. Ltd.

Yahoo Software Development India Pvt. Ltd.
New Job Vacancy in YAHOO....

Job Description
The Internet is a big, busy place, and we at Yahoo! are proud to stand out in the crowd. As the world’s number one Internet brand, servicing over a half billion people, we’re determined to maintain our commitment to delivering news, entertainment, information and fun… each and every day.

In order to maintain our position as one of the world’s most trafficked Internet destinations, we’re always on the lookout for people with big ideas and big talent to help us provide our visitors with the innovative products and services they’ve come to expect from Yahoo!. We’re looking for people like you.

How Big Can You Think?

Do you enjoy solving highly technical and challenging problems?
Are you excited about the world of e-commerce?
Do you want to be part of a team that is considered a leader in the US Small Business market?

Yahoo! Small Business is looking for energetic and experienced who is passionate about building the next generation, scalable, reliable and high performance e-commerce web application services. Our services support tens of thousands of small business with billions of dollars in sales.

The service must be fast, highly available, customizable, and built to scale. This poses very interesting challenges with browser technologies, distributed programming, large-volume system architecture, efficient program design and security.

A successful candidate must be passionate about his area of expertise, a fast learner, self-starter, and a skilled problem solver.

As an architect, you will provide technical leadership to the team. You will work closely with senior management, engineering and business teams to solve a wide-range of issues, understand broad concepts and make them a reality. You will define best practices and ensure the overall quality of the system architecture and design. You should be able to make significant contribution to backend systems including architecture, design and coding and will be called upon to solve critical production issues.
Desired Candidate Profile
Minimum Qualifications:
* Talent and passion for architecting concepts into reality.
* Excel at solving problems ranging from application design to large system deployment.
* In-depth understanding of transactional systems, data storage technologies, disk/network performance tradeoffs, caching strategies, failover, performance tuning, internet and distributed system architecture.
* Excellent communication and interpersonal skills.
* BS/MS/PhD in Computer Science with relevant work experience of which at least 2-3 years is as an architect for a significantly complex product/service.

Recommended Qualifications:
* Experience optimizing runtime performance and memory size.
* Experience with parallel processing, multithreading, and shared memory.
* Experience with Apache, HTTP protocol and internet technologies.
* Experience UNIX system programming.
* Expertise with object-oriented design, C++, PHP and/or PERL.
* Experience with relational databases especially MySQL.

Some travel may be required.
Company Profile
At Yahoo!, we look at life in a different way. Everything inspires us: from a train ticket to the beverage we drink. Equations, Algorithms, Indexes, Terabytes of data; we see them everywhere. No wonder our product teams in Bangalore have been able to churn out a host of innovations: Yahoo! Podcasts, Yahoo! Audio Search, Yahoo! Hotjobs, Yahoo! SpamGuard+, Behavioral Targeting, consumer centric data driven products and marketing applications to name a few. So to name a few. So, if you wish to get aboard the innovation engine, just walk-in at the below mentioned venue.
Contact Details

Company Name:
Yahoo Software Development India Pvt. Ltd.

Website:
Not Mentioned

Address:
Not Mentioned

Telephone:
Not Mentioned

Reference ID:
15367

read more...

Triggering and Handling Events

In ABAP Objects, triggering and handling an event means that certain methods act as triggers and trigger events, to which other methods - the handlers - react. This means that the handler methods are executed when the event occurs.

This section contains explains how to work with events in ABAP Objects. For precise details of the relevant ABAP statements, refer to the corresponding keyword documentation in the ABAP Editor.

Triggering Events

To trigger an event, a class must

Declare the event in its declaration part
Trigger the event in one of its methods
Declaring Events

You declare events in the declaration part of a class or in an interface. To declare instance events, use the following statement:

EVENTS EXPORTING… VALUE() TYPE type [OPTIONAL]..

To declare static events, use the following statement:

CLASS-EVENTS …

Both statements have the same syntax.

When you declare an event, you can use the EXPORTING addition to specify parameters that are passed to the event handler. The parameters are always passed by value. Instance events always contain the implicit parameter SENDER, which has the type of a reference to the type or the interface in which the event is declared.

Triggering Events

An instance event in a class can be triggered by any method in the class. Static events can be triggered by any static method. To trigger an event in a method, use the following statement:

RAISE EVENT EXPORTING… = …

For each formal parameter that is not defined as optional, you must pass a corresponding actual parameter in the EXPORTING addition. The self-reference ME is automatically passed to the implicit parameter SENDER.

Handling Events

Events are handled using special methods. To handle an event, a method must

be defined as an event handler method for that event
be registered at runtime for the event.
Declaring Event Handler Methods

Any class can contain event handler methods for events from other classes. You can, of course, also define event handler methods in the same class as the event itself. To declare an event handler method, use the following statement:

METHODS FOR EVENT OF IMPORTING.. ..

for an instance method. For a static method, use CLASS-METHODS instead of METHODS. is an event declared in the class or interface .

The interface of an event handler method may only contain formal parameters defined in the declaration of the event . The attributes of the parameter are also adopted by the event. The event handler method does not have to use all of the parameters passed in the RAISE EVENT statement. If you want the implicit parameter SENDER to be used as well, you must list it in the interface. This parameter allows an instance event handler to access the trigger, for example, to allow it to return results.

If you declare an event handler method in a class, it means that the instances of the class or the class itself are, in principle, able to handle an event triggered in a method.

Registering Event Handler Methods

To allow an event handler method to react to an event, you must determine at runtime the trigger to which it is to react. You can do this with the following statement:

SET HANDLER… … [FOR]…

It links a list of handler methods with corresponding trigger methods. There are four different types of event.

It can be

An instance event declared in a class
An instance event declared in an interface
A static event declared in a class
A static event declared in an interface
The syntax and effect of the SET HANDLER depends on which of the four cases listed above applies.

For an instance event, you must use the FOR addition to specify the instance for which you want to register the handler. You can either specify a single instance as the trigger, using a reference variable :

SET HANDLER… …FOR .

or you can register the handler for all instances that can trigger the event:

SET HANDLER… …FOR ALL INSTANCES.

The registration then applies even to triggering instances that have not yet been created when you register the handler.

You cannot use the FOR addition for static events:

SET HANDLER… …

The registration applies automatically to the whole class, or to all of the classes that implement the interface containing the static event. In the case of interfaces, the registration also applies to classes that are not loaded until after the handler has been registered.

Timing of Event Handling

After the RAISE EVENT statement, all registered handler methods are executed before the next statement is processed (synchronous event handling). If a handler method itself triggers events, its handler methods are executed before the original handler method continues. To avoid the possibility of endless recursion, events may currently only be nested 64 deep.

Handler methods are executed in the order in which they were registered. Since event handlers are registered dynamically, you should not assume that they will be processed in a particular order. Instead, you should program as though all event handlers will be executed simultaneously.

read more...

What is source inspection?

What is source inspection and what are the setup required to do in system to implement successfully?

A source inspection is a quality inspection in which Buyer required the quality check before the material received. So that he performed the quality inspection at the vendor’s Location.

To setup source inspection, you should define inspection type (01 and 0101) in material master QM View. (MM01)

When requesting source inspection, include the following information:

a) Purchase order number
b) Item number
c) Part number
d) Quantity of parts to be inspected
e) Date source inspection is required
f) Types of inspection required
- In Process
- Final
- Interim
- First Article Inspection (FAI)
g) Contact name and phone number

Go to transaction QI07 and give the material code, vendor, plant and opening period. When you execute the transaction you would find open purchase orders for the given input data. Select the Purchase Order you wish to perform Source Inspection and choose Create Inspection Lot. These inspection lot triggers for inspection type 0101. Against this inspection Lot perform result recording QE01 & QA11.

When finally you received Goods at your premises, then inspection lot will triggered automatically (01) and perform result recording QE01 & QA11

read more...

PROCEDURE USED FOR SOURCE INSPECTION IN QM

What's the process for source inspection?

The Q-Info Record is used to trigger a source inspection lot for a material or vendor and plant. Under the tab key Inspection Controls in Record of Q-Info, you would find vendor source Inspection and under that select the inspection type desired for source inspection (say 01,0101) and give the lead time required to perform the inspection in days (say 10 days).

If you do not want to trigger an inspection more @ GR for a source Inspection lot then check the box (Source Insp. No Gr).

Ensure that the inspection type selected at source inspection is activated in the Material Master Record for the chosen material in the Quality Management View.

To trigger the lot manually you need to have some open purchase orders for the material/plant/vendor. Go to transaction QI07 and give the material code, vendor, plant and opening period.

When you execute the transaction you would find open purchase orders for the given input data. Select the Purchase Order you wish to perform Source Inspection and choose Create Inspection Lot.

This would trigger the lot and then it is QE01 & QA11

We have an in-process inspection set in the PP routing. We have three MIC's attached that take varying amounts of completion time. SAP will also allow confirmation of that step when only one of the MIC's has been entered. We need the system to NOT allow confirmation (in CO11N) until the UD is made.

The following steps also can be done if more than one operation is there in routing.

1. The operation which requires inspection completion need to be given with the control key having milestone for confirmation.
2. In SPRO-Producion-shop floor control-Operation- Define confirmation parameters, select the order type that will be used for production.
3. In detail screen, In check area - for Results Rec.QM field,change to error message if no inspection results exists.
4. The system will check, if any result recording has been carried out for that operation.
5. The drawback will be, if one MIC is recorderd and others left without value, still the system will allow to confirm the production order.

The above holds good only if there are more than 1 operation. if one operation is there in the routing, directly we can activate the "04 inspection type" for the material and move to quality stock during final confirmation.

read more...

SOURCE INSPECTION IN QM

Can any one guide how to do Source Inspection in QM. What are the settings required to be done and can the lot for source inspection be trigerred manually or automatically.

The Q-Info Record is used to trigger a source inspection lot for a material/vendor and plant. Under the tab key Inspection Control in Q-Info Record, you would find vendor source Inspection and under that select the inspection type desired for source inspection (say 01,0101) and give the lead time required to perform the inspection in days (say 10 days). If you do not want to trigger an inspection lot @ GR for a source Inspection lot then check the box (Source Insp. No Gr).

Ensure that the inspection type selected @ source inspection is activated in the Material Master Record for the chosen material in the Quality Management View.

To trigger the lot manually you need to have some open purchase orders for the material/plant/vendor. Go to transaction QI07 and give the material code,vendor,plant and opening period. When you execute the transaction you would find open purchase orders for the given input data. Select the Purchase Order you wish to perform S.I and choose Create Inspection Lot.

This would trigger the lot and then it is QE01 & QA11.

Two more questions ..

1. Purchase order for this material (which has to undergo source inspection) will show open order qty until GR is
posted for this material.Inspection lot created thru QI07 is not stock posting relevant i.e. you can not post the
quantity to Unrestricted use stock.The procedure you have mentioned allows you to record results but in
the UD there is no Stock posting tab thru which you can post the material to Unrestricted use stock. How
will you take care regarding posting of this material to Unrestricted stock.

2. Can we have inspection type 01(GR insp for PO) & 0101 (Source Inspection) activated at the same time in the
Material master record for a material.Have you come across such a scenario.What will be the implication if
both the inspection types are activated.

1) Source Inspection(SI): Well, you need to understand the concept and use of Source Inspection. The inspection lots created using this are not stock relevant as the material is not inward thru GR at the point when these lots are triggered. Hence the UD will not have a stock posting tab and if you want a stock posting tab then it becomes normal inspection (01). Hope you understand the difference, also after results record & UD if you decide not to have a inspection lot triggered @ GR then you need to update it in the Q-Info record. The settings for this scenario are already given below.

2) Inspection type (01,0101) can be activated @ the same time.In addition to this you can have a preferred indicator set for the inspection type you want to be selected when you perform goods receipt.
This check box is available in the inspection type set up in the Material master. If you do not check the preferred inspection type then the variant 01 for lot origins 01 is given preference.

If you want an inspection type 0101 to be triggered @ SI then you need to define this in the Q-Info record.

read more...

Set Up for Credit Card Payment Processing

Given below is the set up for credit card payment processing:

Set Up Credit Control Areas:

Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be ‘00012’. This entry is required so the sales order will calculate the value to authorize

Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code

Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used

Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: “A”
Reqt: “2”
AltCTy: “4”

Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field “no Credit Check” with the valid number for sales documents.

Set Up Payment Guarantees

Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form “02” defined for payment cards. Other than the descriptor, the only other entry should be “3” in the column labeled “PymtGuaCat”

Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number “1”
Payment Guarantee Form “02”
Routine Number “0” Routine Number can be used to validate payment card presence.

Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment Cards)”.

Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards

Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.

Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure

Payment Card Configuration

Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etc…)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month

The Routines can be created based on the original routines delivered by SAP.

*****SAP does not deliver a card check for Discover Card. We created our own routine.

Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check

Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.

Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999

American Express Credit Expires in 30 days
340000 349999
370000 379999

Discover Card Credit Expires in 30 days
601100 601199

Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each type which can accept a payment card

Configuration for Authorization Request

Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).

Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.

Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards

Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.

AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7

Configuration for clearing houses

Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.

Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence “A001”

Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.

Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.

Authorization and Settlement Control

Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.

Enter Merchant ID’s
Transaction:
Tables: TCCM
Action: Create the merchant id’s that the company uses to process payment cards

Assign merchant id’s
Transaction:
Tables: TCCAA
Action: Enter the merchant id’s with each clearinghouse account

read more...