[rtc-linux] SAP SD OTC Consultant @ St Louis, MO

2018-04-19 Thread Srikanth HCL Global 
Hello,



Greetings of the day!!!



*Please share resumes to* *s...@hclglobal.com* * at
earliest.*



*Below is the job description for your consideration:*

*JD as follows:*

Role: SAP SD OTC   Consultant

Location: St Louis, MO

Duration: 6 - 12 months

Rate: $DOE/hr



· 8-10 Years of SAP O2C with EDI Skills.

· Work with process leads to understand pain points and provide
improvement/efficiency opportunities throughout the SD functions.

· Extensive knowledge & Experience with SAP S4 and integration with
MDG, GTS, and EWM

· Project management and presentation skills, superior analytical,
evaluative, and problem-solving abilities as well as exceptional customer
service orientation.

· Deep experience in OTC workstream objects including SD Quotation
SD Contracts, Listing & Exclusions PM, WM is essential

-- 
Thanks & Regards,


Srikanth,

HCL Global Systems, Inc

24543 Indoplex Circle,


Suite 220, Farmington. MI 48335


Board- 248-473-0720 Ext: 179

Email Id: s...@hclglobal.com

-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups 
"rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rtc-linux+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rtc-linux] [abelloni:rtc-next 1/3] drivers//rtc/rtc-cmos.c:863:4: error: implicit declaration of function 'use_hpet_enabled'; did you mean 'is_hpet_enabled'?

2018-04-19 Thread kbuild test robot 
tree:   https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git 
rtc-next
head:   2394261b480c677380df432a1c1a712eeb25f386
commit: 294e17d1a6ae28f1d11f93f92b76c37bb9083968 [1/3] rtc: cmos: allow using 
ACPI for RTC alarm instead of HPET
config: x86_64-randconfig-x015-201815 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
git checkout 294e17d1a6ae28f1d11f93f92b76c37bb9083968
# save the attached .config to linux build tree
make ARCH=x86_64 

All errors (new ones prefixed by >>):

   In file included from include/linux/platform_device.h:14:0,
from drivers//rtc/rtc-cmos.c:39:
   drivers//rtc/rtc-cmos.c: In function 'cmos_do_probe':
>> drivers//rtc/rtc-cmos.c:863:4: error: implicit declaration of function 
>> 'use_hpet_enabled'; did you mean 'is_hpet_enabled'? 
>> [-Werror=implicit-function-declaration]
   use_hpet_enabled() ? ", hpet irqs" : "");
   ^
   include/linux/device.h:1382:58: note: in definition of macro 'dev_info'
#define dev_info(dev, fmt, arg...) _dev_info(dev, fmt, ##arg)
 ^~~
   cc1: some warnings being treated as errors

vim +863 drivers//rtc/rtc-cmos.c

   688  
   689  static int INITSECTION
   690  cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq)
   691  {
   692  struct cmos_rtc_board_info  *info = dev_get_platdata(dev);
   693  int retval = 0;
   694  unsigned char   rtc_control;
   695  unsignedaddress_space;
   696  u32 flags = 0;
   697  struct nvmem_config nvmem_cfg = {
   698  .name = "cmos_nvram",
   699  .word_size = 1,
   700  .stride = 1,
   701  .reg_read = cmos_nvram_read,
   702  .reg_write = cmos_nvram_write,
   703  .priv = _rtc,
   704  };
   705  
   706  /* there can be only one ... */
   707  if (cmos_rtc.dev)
   708  return -EBUSY;
   709  
   710  if (!ports)
   711  return -ENODEV;
   712  
   713  /* Claim I/O ports ASAP, minimizing conflict with legacy driver.
   714   *
   715   * REVISIT non-x86 systems may instead use memory space 
resources
   716   * (needing ioremap etc), not i/o space resources like this ...
   717   */
   718  if (RTC_IOMAPPED)
   719  ports = request_region(ports->start, 
resource_size(ports),
   720 driver_name);
   721  else
   722  ports = request_mem_region(ports->start, 
resource_size(ports),
   723 driver_name);
   724  if (!ports) {
   725  dev_dbg(dev, "i/o registers already in use\n");
   726  return -EBUSY;
   727  }
   728  
   729  cmos_rtc.irq = rtc_irq;
   730  cmos_rtc.iomem = ports;
   731  
   732  /* Heuristic to deduce NVRAM size ... do what the legacy NVRAM
   733   * driver did, but don't reject unknown configs.   Old hardware
   734   * won't address 128 bytes.  Newer chips have multiple banks,
   735   * though they may not be listed in one I/O resource.
   736   */
   737  #if defined(CONFIG_ATARI)
   738  address_space = 64;
   739  #elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) \
   740  || defined(__sparc__) || defined(__mips__) \
   741  || defined(__powerpc__)
   742  address_space = 128;
   743  #else
   744  #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes.
   745  address_space = 128;
   746  #endif
   747  if (can_bank2 && ports->end > (ports->start + 1))
   748  address_space = 256;
   749  
   750  /* For ACPI systems extension info comes from the FADT.  On 
others,
   751   * board specific setup provides it as appropriate.  Systems 
where
   752   * the alarm IRQ isn't automatically a wakeup IRQ (like ACPI, 
and
   753   * some almost-clones) can provide hooks to make that behave.
   754   *
   755   * Note that ACPI doesn't preclude putting these registers into
   756   * "extended" areas of the chip, including some that we won't 
yet
   757   * expect CMOS_READ and friends to handle.
   758   */
   759  if (info) {
   760  if (info->flags)
   761  flags = info->flags;
   762  if (info->address_space)
   763  address_space = info->address_space;
   764  
   765  if (info->rtc_day_alarm && info->rtc_day_alarm < 128)
   766

[rtc-linux] [abelloni:rtc-next 1/3] drivers/rtc/rtc-cmos.c:863:4: error: implicit declaration of function 'use_hpet_enabled'

2018-04-19 Thread kbuild test robot 
tree:   https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git 
rtc-next
head:   2394261b480c677380df432a1c1a712eeb25f386
commit: 294e17d1a6ae28f1d11f93f92b76c37bb9083968 [1/3] rtc: cmos: allow using 
ACPI for RTC alarm instead of HPET
config: i386-randconfig-s0-201815 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
git checkout 294e17d1a6ae28f1d11f93f92b76c37bb9083968
# save the attached .config to linux build tree
make ARCH=i386 

All errors (new ones prefixed by >>):

   In file included from include/linux/platform_device.h:14:0,
from drivers/rtc/rtc-cmos.c:39:
   drivers/rtc/rtc-cmos.c: In function 'cmos_do_probe':
>> drivers/rtc/rtc-cmos.c:863:4: error: implicit declaration of function 
>> 'use_hpet_enabled' [-Werror=implicit-function-declaration]
   use_hpet_enabled() ? ", hpet irqs" : "");
   ^
   include/linux/device.h:1382:58: note: in definition of macro 'dev_info'
#define dev_info(dev, fmt, arg...) _dev_info(dev, fmt, ##arg)
 ^~~
   cc1: some warnings being treated as errors

vim +/use_hpet_enabled +863 drivers/rtc/rtc-cmos.c

   688  
   689  static int INITSECTION
   690  cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq)
   691  {
   692  struct cmos_rtc_board_info  *info = dev_get_platdata(dev);
   693  int retval = 0;
   694  unsigned char   rtc_control;
   695  unsignedaddress_space;
   696  u32 flags = 0;
   697  struct nvmem_config nvmem_cfg = {
   698  .name = "cmos_nvram",
   699  .word_size = 1,
   700  .stride = 1,
   701  .reg_read = cmos_nvram_read,
   702  .reg_write = cmos_nvram_write,
   703  .priv = _rtc,
   704  };
   705  
   706  /* there can be only one ... */
   707  if (cmos_rtc.dev)
   708  return -EBUSY;
   709  
   710  if (!ports)
   711  return -ENODEV;
   712  
   713  /* Claim I/O ports ASAP, minimizing conflict with legacy driver.
   714   *
   715   * REVISIT non-x86 systems may instead use memory space 
resources
   716   * (needing ioremap etc), not i/o space resources like this ...
   717   */
   718  if (RTC_IOMAPPED)
   719  ports = request_region(ports->start, 
resource_size(ports),
   720 driver_name);
   721  else
   722  ports = request_mem_region(ports->start, 
resource_size(ports),
   723 driver_name);
   724  if (!ports) {
   725  dev_dbg(dev, "i/o registers already in use\n");
   726  return -EBUSY;
   727  }
   728  
   729  cmos_rtc.irq = rtc_irq;
   730  cmos_rtc.iomem = ports;
   731  
   732  /* Heuristic to deduce NVRAM size ... do what the legacy NVRAM
   733   * driver did, but don't reject unknown configs.   Old hardware
   734   * won't address 128 bytes.  Newer chips have multiple banks,
   735   * though they may not be listed in one I/O resource.
   736   */
   737  #if defined(CONFIG_ATARI)
   738  address_space = 64;
   739  #elif defined(__i386__) || defined(__x86_64__) || defined(__arm__) \
   740  || defined(__sparc__) || defined(__mips__) \
   741  || defined(__powerpc__)
   742  address_space = 128;
   743  #else
   744  #warning Assuming 128 bytes of RTC+NVRAM address space, not 64 bytes.
   745  address_space = 128;
   746  #endif
   747  if (can_bank2 && ports->end > (ports->start + 1))
   748  address_space = 256;
   749  
   750  /* For ACPI systems extension info comes from the FADT.  On 
others,
   751   * board specific setup provides it as appropriate.  Systems 
where
   752   * the alarm IRQ isn't automatically a wakeup IRQ (like ACPI, 
and
   753   * some almost-clones) can provide hooks to make that behave.
   754   *
   755   * Note that ACPI doesn't preclude putting these registers into
   756   * "extended" areas of the chip, including some that we won't 
yet
   757   * expect CMOS_READ and friends to handle.
   758   */
   759  if (info) {
   760  if (info->flags)
   761  flags = info->flags;
   762  if (info->address_space)
   763  address_space = info->address_space;
   764  
   765  if (info->rtc_day_alarm && info->rtc_day_alarm < 128)
   766  cmos_rtc.day_alrm =

[rtc-linux] SAP Vistex ABAP- Technical Consultant || St Paul, MN

2018-04-19 Thread Srikanth HCL Global 
Hello,



Greetings of the day!!!



*Please share resumes to* *s...@hclglobal.com* * at
earliest.*



*Below is the job description for your consideration:*

*JD as follows:*


Title: SAP Vistex ABAP- Technical Consultant
Location: St Paul, MN
Duration: 6 - 12 Months
Rate $DOE/hr

*5-6 years in ABAP*
*3-4 years in Vistex*

• SAP Vistex ABAP - Technical Consultant: Design, Implement, test and
supports SAP Vistex functionality(Bill backs, Customer Rebates and Sales
Incentives)
• Supports the design with strong working knowledge of SD OTC Pricing
Analysis, EDI Order processing, Delivery processing and FI Integration

• Knowledge/experience in SAP Vistex, SD pricing, OTC, and Finance
areas are a plus
- Ability to learn new software quickly
-Ability to work in a fast-paced environment and within tight deadlines
-Independent thinking with keen problem-solving skills
-Excellent communication and client handling skills
-Vistex experience is a must
Bachelors Degree or equivalent


-- 
Thanks & Regards,


Srikanth,

HCL Global Systems, Inc

24543 Indoplex Circle,

Suite 220, Farmington. MI 48335

Board- 248-473-0720 Ext: 179

Email Id: s...@hclglobal.com

-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups 
"rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rtc-linux+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rtc-linux] SAP TMS Consultant @ St Louis MO

2018-04-19 Thread Srikanth HCL Global 
Hello,



Greetings of the day!!!



*Please share resumes to* *s...@hclglobal.com* * at
earliest.*



*Below is the job description for your consideration:*

*JD as follows:*


Role: SAP TMS Consultant
Location: St Louis MO
Duration: 6 - 12 Months
Rate: $DOE/hr

Perform SAP TM system research, configuration, and integration with SAP
ECC. Also includes assisting with new warehouse setup, writing interfaces,
and assisting with configuration of middleware and outside warehouse
applications.
Create functional specifications for Technical Developers in design and
development of forms, input templates, and reports. Participate in
technical reviews to validate designs involved in SAP TM implementation.
Execute system testing during required test cycles as well as day to day
enhancement/defect testing for areas including TM Planning and ECC Shipment
Execution.
Understand end users' business needs, define requirements using existing
SAP templates for manufacturing plants/system enhancements, and communicate
these to SAP functional teams and business users.
Create opportunities for efficiency and improved user experience in SAP TM.
Perform other duties as assigned.

Qualifications:
3+ years of functional/configuration experience in SAP-TM
At least 1 life cycle implementation of SAP ECC and TM
Experience supporting manufacturing plant personnel with day-to-day ERP
system processes
Experience supporting Transportation Planners with day-to-day SAP TM system
processes
Over 2 years Transportation experience or Transportation Management System
administration
Flexibility, adaptability, and process improvement approach
Technical proficiency in Microsoft Office
Strong written and verbal communication skills

-- 
Thanks & Regards,


Srikanth,

HCL Global Systems, Inc

24543 Indoplex Circle,

Suite 220, Farmington. MI 48335

Board- 248-473-0720 Ext: 179

Email Id: s...@hclglobal.com

-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups 
"rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rtc-linux+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.